---
schema_version: "1"
id: 168e7721ce2decdfba78a2c564dceef3fecb4548b9eb86d33cdaf244f53ae366
title: Inclusive Terms Are Replacing Legacy Language
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/commerce/264-0-0/b2c_inclusive_terms.md
canonical_url: https://help.salesforce.com/s/articleView?id=commerce.b2c_inclusive_terms.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 3cbba02c1e300f6bd80155b5cc5e3738055e739860c66927bc96cdd80e12052a
description: As part of our efforts to refine language in our products to more accurately reflect inclusivity, Salesforce is replacing terms deemed noninclusive. APIs and older API documentation aren’t included because changing terms in our code can break current implementations.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# Inclusive Terms Are Replacing Legacy Language

As part of our efforts to refine language in our products to more accurately reflect inclusivity, Salesforce is replacing terms deemed noninclusive. APIs and older API documentation aren’t included because changing terms in our code can break current implementations.

Where: This change applies to all versions of Salesforce B2C Commerce and B2C Commerce services in Production, Sandbox, and Development instances.

When: Starting with the B2C Commerce 20.7 release.

Feature Impact: Enabled for administrators and developers.

Why: Equality is a core value at Salesforce. To ensure that language in Salesforce content and products is more inclusive, we continue to make updates and communicate them in the release notes.

How: To learn more about terms that are changing, see [How we’re bringing inclusive language to our products](https://www.salesforce.com/news/stories/how-were-bringing-inclusive-language-to-our-products/).