Merge branch 'main' into main

content/en-us/production/analytics/engagement.md

@@ -51,3 +51,12 @@ Performance is how well your experience runs on different devices and platforms.
 3. **Set up a user community** that can help identify bugs and crashes.
 
 You can grow your experience faster if it's more engaging to both new and existing users. For more information on retaining your users for engagement, see [Retention](../../production/analytics/retention.md).
+
+## Improving New User First Session Retention
+
+The New User First Session Retention chart shows how many new users are still playing X minutes after joining your experience for the first time. It compares the current period with the previous period. You can use it to generate insights and catch issues with your experience's onboarding.
+
+For instance, if your chart shows that the percentage of new users still playing after 5 minutes decreased significantly week-on-week, you could explore the following potential causes:
+
+1. **Look into new user onboarding friction** from any recent updates. Did you add a new step, or change any introductory messaging?
+2. **Check [error](./error-report.md) and [performance](./performance.md) reports** to see if there has been any change in performance or stability after a recent update.

content/en-us/production/localization/automatic-translations.md

@@ -73,6 +73,24 @@ Once strings are captured to your localization table, follow these steps to enab
 Roblox has initial and monthly quotas for automatic translation. The quotas determine how many string entries you can translate per language. The initial quota determines to how many string entries you can translate via automatic translations when you localize your experience for the first time. After you use up the initial quota, any subsequent translations come from your monthly quota, which resets every month.
 </Alert>
 
+## Automatic Translation Updates
+
+As the automatic translation tool improves, more accurate translations may become available for existing strings. When these updates become available, Roblox refreshes any automatic translations. Automatic translation updates will appear in your translation history.
+
+<img src="../../assets/localization/Update-Log.png"
+     width="800" alt="A translation history log displays at the bottom of each translation entry."/>
+
+If you have a specific translation that you want to remain unchanged, you can lock the entry to ensure it will not be impacted by any updates.
+
+<img src="../../assets/localization/Lock-Translations.png"
+     width="800" alt="A 'Lock translation from automatic updates' toggle is accessible below the translation entry field in each translation entry."/>
+
+<Alert severity = 'warning'>
+By locking an entry, you are approving the translation and turning it into a manual entry. This means it will not be impacted by any automatic translation updates, including safety-related updates. If, in the future, it is discovered that the translation violates policy, your experience will still be subject to moderation.
+</Alert>
+
+By default, manually added strings and strings with manual translations are locked. If you unlock an entry, it will be impacted by both automatic translation updates and ATC if it is enabled. If you want to generate a new automatic translation for a previously changed or cleared translation, unlock the entry.
+
 ## Supported Languages
 
 Roblox supports automatic translation with the following languages:

content/en-us/scripting/data/player-data-purchasing.md

@@ -44,7 +44,11 @@ Roblox has reference code to assist you with designing and building player data
 
 <a href="https://create.roblox.com/marketplace/asset/14376223840/Purchase-Handling)">
   <Button variant="contained">Get the Code</Button>
-</a>
+</a><br />
+
+After you import the model into Studio, you should see the following folder structure:
+
+<img src="../../assets/data/player-data-purchasing/Sample-Hierarchy.png" alt="Explorer window showing the purchasing system model." width="320" />
 
 ## Architecture
 
@@ -54,7 +58,7 @@ This high-level diagram illustrates the key systems in the sample and how they i
 
 ## Retries
 
-**Class:** `DataStoreWrapper`
+**Class:** [`DataStoreWrapper`](#sample-code)
 
 ### Background
 
@@ -124,7 +128,7 @@ Ultimately, our view is that the simple approach (processing every request) is p
 
 ## Session Locking
 
-**Class:** `SessionLockedDataStoreWrapper`
+**Class:** [`SessionLockedDataStoreWrapper`](#sample-code)
 
 ### Background
 
@@ -188,7 +192,7 @@ If the lock expiry time has been exceeded without the lock being updated, then a
 
 ## Developer Product Processing
 
-**Singleton:** `ReceiptHandler`
+**Singleton:** [`ReceiptHandler`](#sample-code)
 
 ### Background
 
@@ -246,7 +250,7 @@ The comments in `ReceiptProcessor` outline the approach:
 
 ## Player Data
 
-**Singletons:** `PlayerData.Server`, `PlayerData.Client`
+**Singletons:** [`PlayerData.Server`](#sample-code), [`PlayerData.Client`](#sample-code)
 
 ### Background