fix: comments from Dymytro & Nick

Author: chris-nowicki

docs/storefront/catalyst/content-management/internationalization/multi-language/overview.mdx

@@ -18,7 +18,7 @@ BigCommerce supports multiple locales for shoppers in different regions.
 * Add translations for categories and locations to multiple locales added to Catalyst channel. Learn about how to use the [GraphQL Admin API](https://developer.bigcommerce.com/docs/store-operations/translations) to add translations to a single channel and locale.
 
 <Callout type="info">
-  Managing locales (in Control Panel, CLI, or via the GraphQL Admin API) is available for Catalyst channels. As of `October 2025`, new stores have the multi-language feature enabled by default. On stores where multi-language is disabled, locale mutations and Channel Manager locale controls aren't available.
+  Managing locales (in Control Panel, CLI, or via the GraphQL Admin API) is available for Catalyst channels. As of `October 2025`, all Catalyst stores have the multi-language feature enabled by default. On stores where multi-language is disabled, locale mutations and Channel Manager locale controls aren't available.
 </Callout>
 
 ## Default Catalyst features

docs/storefront/catalyst/content-management/internationalization/multi-language/setup.mdx

@@ -13,11 +13,11 @@ Follow the [Getting Started with Catalyst](/docs/storefront/catalyst/getting-sta
 ## Adding a locale in Catalyst
 
 <Callout type="info">
-  **Control Panel access:** The Localization tab in Channel Manager for adding/removing locales is available for Catalyst channels.
-  **Default:** On newly created stores, multi-language is enabled by default.
+  **Control Panel access:** The Localization tab in Channel Manager for adding/removing locales is available for Catalyst channels in **Settings** > **Localization** or via editing the channel in **Channel Manager**.
+  **Default:** multi-language is enabled by default on all Catalyst stores.
 </Callout>
 
-You can add additional languages to your storefront when you initially create your Catalyst storefront through the Control Panel. If you didn’t do so, you have a couple of options.
+You can add additional languages to your storefront when you initially create your Catalyst storefront through the Control Panel. If you didn't do so, you have a couple of options.
 
 You can enable more locales for your storefront through the Control Panel:
 

docs/storefront/headless/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: Introduction to Headless Commerce
-keywords: headless, commerce, storefronts, backend, frontend, whitepaper, api, sdk, 
+keywords: headless, commerce, storefronts, backend, frontend, whitepaper, api, sdk,
 ---
 
 # Introduction to Headless Commerce
@@ -86,7 +86,7 @@ The following example uses the GraphQL Storefront API to complete a checkout and
       # Correlation header matches next request
       X-Correlation-Id: a7d28ca2-d4b2-4dc8-9f07-0706c431a372
     ```
-    
+
     ```graphql {5} filename="Example mutation: Complete checkout" showLineNumbers copy
       mutation completeCheckout($completeCheckoutInput: CompleteCheckoutInput!) {
         checkout {
@@ -107,7 +107,7 @@ The following example uses the GraphQL Storefront API to complete a checkout and
     ```
   </Tab>
   <Tab>
-    
+
     ```json {6-7} filename="Example mutation: Complete checkout" showLineNumbers copy
       {
         "data": {
@@ -148,10 +148,10 @@ The following example uses the GraphQL Storefront API to complete a checkout and
       }
 
     ```
-    
+
   </Tab>
   <Tab>
-    
+
     ```json filename="Example response: Process payment" showLineNumbers copy
       {
         "data": {
@@ -173,7 +173,7 @@ BigCommerce has introduced a feature that leverages the [Customer Access Token](
   After three attempts with invalid session-sync JWT tokens, the system will block the IP address for five minutes.
 </Callout>
 
-The following examples demonstrate how to sync and validate session details for headless storefronts and hosted checkouts.    
+The following examples demonstrate how to sync and validate session details for headless storefronts and hosted checkouts.
 
 <Tabs items={['Format', 'Mutation', 'Validate']}>
   <Tab>
@@ -187,7 +187,7 @@ The following examples demonstrate how to sync and validate session details for
 
 mutation GenerateSessionSyncJwt ($redirectTo: String!,$cartId: String,$visitorId: String,$ipAddress: IpAddress){
    generateSessionSyncJwt(redirectTo:$redirectTo,cartId: $cartId, visitorId: $visitorId, ipAddress: $ipAddress){
-      result { 
+      result {
         token
         url
         }
@@ -196,7 +196,7 @@ mutation GenerateSessionSyncJwt ($redirectTo: String!,$cartId: String,$visitorId
 ```
 </Tab>
   <Tab>
-    
+
 ```json # Low-level session sync JWT generation
 # Returns JUST a JWT, *not* a URL
 # Can "sync" any arbitrary combination of parameters
@@ -216,22 +216,22 @@ mutation GenerateSessionSyncJwt {
   </Tab>
 
    <Tab>
-```json # 
+```json #
 mutation ValidateJwt{
   validateSessionSyncJwt(jwt: "eyJ0eXAiOiJKV1QiLCJhbGciOiJFUzI1NiJ9.eyJpc3MiOiJCQyIsImlhdCI6MTczMDQwMTc3MiwiZWF0IjoxNzMwNDAxODAyLCJqdGkiOiI2NTI5NDAyMi02MDA4LTRmY2YtOTUxOC03MWE5NjA0MjEyMjgiLCJvcGVyYXRpb24iOiJzZXNzaW9uX3N5bmMiLCJzaWQiOjczMzE5Nywic2Vzc2lvbl9wYXlsb2FkIjp7ImNhcnRfaWQiOm51bGwsImN1c3RvbWVyX2lkIjpudWxsLCJ2aXNpdG9yX2lkIjoiYWJjMTIzIn0sInJlcXVlc3RfaXAiOm51bGwsInJlZGlyZWN0X3RvIjoiaHR0cHM6Ly9iaWdjb21tZXJjZS5zdXBwb3J0L2ZvbyJ9.TAueByfTCdpw3UwwuKElUoeEjYcqCT13H3pt7UzIh6t6682_w4aaz1akS-FOyyOstOUYcjyUPLN5qi04eXXKKA"){
    content{
      analytics{
        visitorId
 }
      cart{
-       entityId    
+       entityId
 }
      customer {
        firstName
 }
      customerAccessToken{
        expiresAt
-       value    
+       value
 }
      redirectTo
      }
@@ -241,12 +241,16 @@ mutation ValidateJwt{
 </Tab>
 </Tabs>
 
-### Persisting analytics session IDs 
+### Persisting analytics session IDs
 
 The GraphQL API supports including a visitor ID when creating a session sync JWT using the `generateSessionSyncJwt` mutation, enhancing tracking consistency across different contexts. The visitor ID acts as a unique identifier that links a user's activity across multiple storefronts, ensuring that analytics session IDs remain persistent as users move across various parts of the storefront (e.g., Catalyst to Stencil) and other digital touchpoints.
 
 Including a visitor ID in session sync requests helps maintain a cohesive session structure, providing more accurate insights into customer behavior. This is especially valuable for businesses leveraging analytics tools to track user interactions across headless storefronts, native checkouts, and other platforms.
 
+## Multi-Language support
+
+After **October 2025**, new headless stores will have access to Multi-language features similar to [Catalyst storefronts](/docs/storefront/catalyst/content-management/internationalization/multi-language/overview).
+
 ## Next step
 
 - [Learn how to create a channel and a channel site](/docs/storefront/headless/channels)