update Open Source Docs from Roblox internal teams

Author: rbx-open-source-docs[bot]

content/en-us/production/promotion/share-links.md

@@ -20,7 +20,7 @@ To create a share link:
 1. In the [Creator Dashboard](https://create.roblox.com/dashboard/creations), go to **Creations** and select the **Share Links** tab.
 2. Click **Create link**.
 3. Enter a unique campaign name and select the experience you want to create a share link for.
-4. <Chip label="optional" size="medium" variant="outlined" /> To enable custom `Class.Player:GetJoinData()|LaunchData`, toggle on **Use custom LaunchData** and enter a `LaunchData` parameter.
+4. <Chip label="OPTIONAL" size="small" variant="outlined" /> To enable custom `Class.Player:GetJoinData()|LaunchData`, toggle on **Use custom LaunchData** and enter a `LaunchData` parameter.
 5. Click **Generate link**.
 
 The new share link generates instantly and is ready to be shared.

content/en-us/production/promotion/social-media-links.md

@@ -15,7 +15,7 @@ To link to social media:
 3. In the left-hand navigation, under **Engagement**, click **Social Links**.
 4. In the **Link Type** field, select the social media type you want to link to.
 5. In the **URL** and **Title** fields, enter the URL to your social media and the descriptive text you want to display to users to tell them what you want to do.
-6. <Chip label="optional" size="small" variant="outlined" color="primary" /> Click the **Add Link** button to add a second or third social link.
+6. <Chip label="OPTIONAL" size="small" variant="outlined" /> Click the **Add Link** button to add a second or third social link.
 7. When ready, click the **Save** button. The social media links immediately display on your experience's main page.
 
    <img src="../../assets/promotion/misc/Social-Links-Example.png" width="540" />

content/en-us/production/publishing/publish-experiences-and-places.md

@@ -3,9 +3,9 @@ title: Experiences and places
 description: Explains how to publish the places in your experience.
 ---
 
+<figure>
 <iframe width="800" height="450" src="https://www.youtube-nocookie.com/embed/_RxK6l2y7Ac" title="YouTube video player" frameborder="0" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
-
-<br />
+</figure><br />
 
 **Experiences** on Roblox are made up of individual **places**, comparable to scenes in Unity or maps in Unreal Engine. Each place contains all components for that portion of the experience, including its specific environment, parts, meshes, scripts, and user interface.
 
@@ -15,7 +15,11 @@ description: Explains how to publish the places in your experience.
 
 ## Publish experiences
 
-By default, publishing a new place creates a new experience. New experiences begin as **private** and are only accessible to you and members of your [group](../../projects/groups.md) with the correct permissions.
+By default, publishing a new place creates a new experience. New experiences begin as **private** and are only accessible to you and members of your [group](../../projects/groups.md) with the correct [permissions](../../projects/groups.md#roles-and-permissions).
+
+<Alert severity="info">
+When creating and collaborating on experiences as part of a [group](../../projects/groups.md), the ability for group members to play/edit/publish experiences is, by default, dependent on their [role permissions](../../projects/groups.md#roles-and-permissions). However, group owners or members with sufficient permissions can adjust access on a per‑experience level. See [configure experiences](#configure-experiences) for details.
+</Alert>
 
 When you're ready to release an experience to a wider audience, you
 can [release it to the public](#release-to-the-public), although beta testing should still be an essential part of your development cycle. Because you're not able to determine which countries have access to an experience, which limits the ability to run beta tests in smaller markets, consider these strategies:
@@ -89,26 +93,51 @@ The [start place](#start-place) of an experience cannot be instantly swapped wit
 
    <img src="../../assets/publishing/experiences-places-assets/Publish-Window-Select-Start-Place.png" width="720" />
 
-1. **(Optional)** If the experience is live, it's recommended that you restart its servers as outlined in [update experiences](#update-experiences).
+1. <Chip label="OPTIONAL" size="small" variant="outlined" /> If the experience is live, it's recommended that you [restart its servers](#update-experiences).
 
 ## Configure experiences
 
-You can customize your experience's settings from the [Creator Dashboard][creatordashboard] or within Studio's **File**&nbsp;⟩ **Game Settings** window. Some settings are only configurable within Studio while others are only configurable on the dashboard.
-
-Most experience settings are configurable from the [Creator Dashboard][creatordashboard], including [localization](../localization/index.md), access settings, [analytics](../analytics/index.md), and [monetization products](../monetization/index.md). You can also fill out the [Maturity & Compliance questionnaire](../promotion/content-maturity.md) required for generating a content maturity label and content descriptors that players use to make informed decisions about what content they interact with. To configure an experience:
-
-1. Select the experience you want to configure from your [list of creations](https://create.roblox.com/dashboard/creations) on the dashboard.
-1. Click on the category you wish to configure from the left-hand navigation.
-
-The **Communication Settings** category allows you to enable **strong language** if your experience receives a **Restricted** maturity label. You can find this under the **Audience** section of the left-hand navigation. Enable the toggle to relax the text chat filter for some strong language in your experience. This also adds a tag above your experience page to warn other users that your experience may include strong language.
-
-<img src="../../assets/publishing/experiences-places-assets/Maturity-Label-Strong-Language.jpg" width="780" alt="Label indicating the experience contains strong language" />
-
-Regardless of whether or not you activate the toggle, players do not face moderation consequences just for using strong language in chat or voice in 17+ games, but they cannot violate [Community Standards](https://en.help.roblox.com/hc/en-us/articles/203313410#safety) and [Terms of Use](https://www.roblox.com/info/terms). For example, players can type an expletive if they are scared by a monster, but they cannot abuse another player using strong language or otherwise.
-
-<Alert severity="warning">
-In-experience assets and experience metadata cannot contain strong language, even if the toggle is on and your experience is rated 17+. If you include strong language in your assets or experience page, your experience will be moderated.
-</Alert>
+Most experience settings are configurable from the [Creator Dashboard][creatordashboard], including [localization](../localization/index.md), access settings, [analytics](../analytics/index.md), and [monetization products](../monetization/index.md). To configure an experience:
+
+1. Select the experience you want to configure from your [list of creations][creatordashboard] on the dashboard.
+2. Click on the category you wish to configure from the left-hand navigation. Some notable sections include:
+
+   <BaseAccordion>
+   <AccordionSummary>
+   <Typography variant="subtitle2">Configure &nbsp;⟩&nbsp; Permissions</Typography>
+   </AccordionSummary>
+   <AccordionDetails>
+   When creating and collaborating on experiences as part of a [group](../../projects/groups.md), abilities granted to group members are, by default, dependent on their [role permissions](../../projects/groups.md#roles-and-permissions). Through the **Permissions** panel, owners or members with sufficient permissions can adjust play/edit/publish access and more on a per‑experience level, such as allowing a limited group role the ability to edit a specific experience even if that role cannot edit all experiences.
+	 
+	 If a per‑experience permission is greyed out, you either do not have access to manage that permission or the selected role has the permission granted globally. Hovering over the information icon will tell you why something is non‑configurable and how to resolve it.
+   </AccordionDetails>
+   </BaseAccordion>
+
+   <BaseAccordion>
+   <AccordionSummary>
+   <Typography variant="subtitle2">Audience &nbsp;⟩&nbsp; Maturity & Compliance</Typography>
+   </AccordionSummary>
+   <AccordionDetails>
+   This section allows you to fill out the questionnaire required for generating a [content maturity](../promotion/content-maturity.md) label and content descriptors that players use to make informed decisions about what content they interact with.
+   </AccordionDetails>
+   </BaseAccordion>
+
+   <BaseAccordion>
+   <AccordionSummary>
+   <Typography variant="subtitle2">Audience &nbsp;⟩&nbsp; Communication Settings</Typography>
+   </AccordionSummary>
+   <AccordionDetails>
+   This section allows you to enable strong language and relax the text chat filter in your experience. Doing so also adds a tag above your experience page to warn other users that your experience may include strong language:
+
+	 <img src="../../assets/publishing/experiences-places-assets/Maturity-Label-Strong-Language.jpg" width="780" alt="Label indicating the experience contains strong language" />
+
+	 Regardless of whether or not you activate the toggle, players do not face moderation consequences just for using strong language in chat or voice in 17+ games, but they cannot violate [Community Standards](https://en.help.roblox.com/hc/en-us/articles/203313410#safety) and [Terms of Use](https://www.roblox.com/info/terms). For example, players can type an expletive if they are scared by a monster, but they cannot abuse another player using strong language or otherwise.
+
+	 <Alert severity="warning">
+   In-experience assets and experience metadata cannot contain strong language, even if the toggle is on and your experience is rated 17+. If you include strong language in your assets or experience page, your experience will be moderated.
+   </Alert>
+   </AccordionDetails>
+   </BaseAccordion>
 
 ## Release to the public
 
@@ -119,7 +148,7 @@ New experiences begin as **private** and are only accessible to you and members
 
    <img src="../../assets/creator-dashboard/Options-Button-Experience-Private.png" width="200" />
 
-1. **(Recommended)** Explore how to provide [Content maturity labels and content descriptors](#content-maturity) for the experience.
+1. <Chip label="RECOMMENDED" size="small" variant="outlined" color="success" /> Explore how to provide [Content maturity labels and content descriptors](#content-maturity) for the experience.
 
 ### Link to experiences
 

content/en-us/projects/groups.md

@@ -76,24 +76,28 @@ Roles created using the legacy [Groups](https://www.roblox.com/groups) pages wil
    <tbody>
      <tr>
       <td>**Play all group experiences**</td>
-      <td>Members with this role can play all experiences owned by the group, whether they're private or public.</td>
+      <td>Members with this role can play all experiences owned by the group, whether they're private or public. Optionally available as a [per‑experience permission][per_experience_permission].</td>
      </tr>
      <tr>
        <td>**Edit all group experiences**</td>
-       <td>Members with this role can edit all experiences and [assets](../projects/assets/index.md) owned by the group. Does not include editing an experience outside of a [collaborative](../projects/collaboration.md) session or saving a place from one experience into another experience.</td>
+       <td>Members with this role can edit all experiences and [assets](../projects/assets/index.md) owned by the group. Does not include editing an experience outside of a [collaborative](../projects/collaboration.md) session or saving a place from one experience into another experience. Optionally available as a [per‑experience permission][per_experience_permission].</td>
      </tr>
      <tr>
        <td>**Edit & publish all group experiences**</td>
-       <td>Members with this role can both edit experiences, as above, and also publish experiences to Roblox.</td>
+       <td>Members with this role can both edit experiences, as above, and also publish experiences to Roblox. Optionally available as a [per‑experience permission][per_experience_permission].</td>
      </tr>
      <tr>
        <td>**View all analytics for group experiences**</td>
-       <td>Members with this role can access the [analytics](../production/analytics/index.md) of all experiences owned by the group, even if they don't have edit access.</td>
+       <td>Members with this role can access the [analytics](../production/analytics/index.md) of all experiences owned by the group, even if they don't have edit access. Optionally available as a [per‑experience permission][per_experience_permission].</td>
      </tr>
      <tr>
        <td>**Create and configure share links**</td>
        <td>Members with this role can create/configure [share links](../production/promotion/share-links.md).</td>
      </tr>
+     <tr>
+       <td>**View Data Stores Manager**</td>
+       <td>Members with this role can access the [Data Stores Manager](../cloud-services/data-stores/data-stores-manager.md).</td>
+     </tr>
      <tr>
        <td>**Configure bans for all group experiences**</td>
        <td>Members with this role can ban and manage banned users for all experiences owned by the group.</td>
@@ -169,8 +173,8 @@ Roles created using the legacy [Groups](https://www.roblox.com/groups) pages wil
    </tbody>
    </table>
 
-3. <Chip label="important" size="medium" variant="outlined" color="warning" /> Click the **Save Changes** button to apply the permission settings.
-4. <Chip label="optional" size="medium" variant="outlined" /> Click the **Settings** tab and choose a color for the role, then click **Save Changes**.
+3. <Chip label="IMPORTANT" size="small" variant="outlined" color="warning" /> Click the **Save Changes** button to apply the permission settings.
+4. <Chip label="OPTIONAL" size="small" variant="outlined" /> Click the **Settings** tab and choose a color for the role, then click **Save Changes**.
 
    <img src="../assets/creator-dashboard/Group-Roles-Settings-Tab.png" width="780" alt="Settings tab indicated for a group role on the Creator Dashboard." />
 
@@ -277,3 +281,5 @@ Group members with permission to edit all group experiences can enable the [Plac
 - Confirm that each member is [assigned the appropriate role](#assign-roles).
 - Check that each group role has the correct [permissions](#roles-and-permissions).
 - Confirm that the [Place Copying](../production/publishing/publish-experiences-and-places.md#allow-copying) setting is disabled before private assets are added.
+
+[per_experience_permission]: ../production/publishing/publish-experiences-and-places.md#configure-experiences

content/en-us/studio/setup.md

@@ -11,8 +11,8 @@ Create immersive 3D experiences on Roblox with **Roblox Studio**, a free applica
 <thead>
 <tr>
 <th></th>
-<th><Chip label="Minimum" size="medium" color="warning" variant="outlined" /></th>
-<th><Chip label="Recommended" size="medium" color="success" variant="outlined" /></th>
+<th><Chip label="MINIMUM" size="medium" color="warning" variant="outlined" /></th>
+<th><Chip label="RECOMMENDED" size="medium" color="success" variant="outlined" /></th>
 </tr>
 </thead>
 <tbody>

content/en-us/ui/on-screen-containers.md

@@ -89,15 +89,15 @@ The `Class.ScreenGui.ResetOnSpawn|ResetOnSpawn` boolean property determines if t
 <tbody>
   <tr>
     <td>`Class.ScreenGui.ResetOnSpawn|ResetOnSpawn` is `true` (default).</td>
-    <td><Chip label="yes" size="small" variant="outlined" color="success" /></td>
+    <td><Chip label="YES" size="small" variant="outlined" color="success" /></td>
   </tr>
 	<tr>
     <td>The `Class.ScreenGui` is an **indirect** descendant of `Class.StarterGui`; for example it's placed inside a `Class.Folder` located within `Class.StarterGui`.</td>
-    <td><Chip label="yes" size="small" variant="outlined" color="success" /></td>
+    <td><Chip label="YES" size="small" variant="outlined" color="success" /></td>
   </tr>
 	<tr>
     <td>`Class.ScreenGui.ResetOnSpawn|ResetOnSpawn` is `false` **and** the `Class.ScreenGui` is a **direct** descendant of `Class.StarterGui`.</td>
-    <td><Chip label="no" size="small" variant="outlined" color="warning" /></td>
+    <td><Chip label="NO" size="small" variant="outlined" color="warning" /></td>
   </tr>
 </tbody>
 </table>

content/en-us/workspace/index.md

@@ -91,7 +91,7 @@ also contain scripts that act on the individual objects of the model.
 
 Within a script, you can access a place's `Class.Workspace` in three different ways, all of which are valid.
 
-- `game:GetService("Workspace")` <Chip label="recommended" size="small" variant="outlined" color="success" />
+- `game:GetService("Workspace")`
 - `workspace`
 - `game.Workspace`