update Open Source Docs from Roblox internal teams

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

content/en-us/education/build-it-play-it-island-of-move/sharing-animations.md

@@ -10,10 +10,10 @@ Share animations with friends and fellow developers by exporting and importing t
 
 <Alert severity="info">
 <AlertTitle>Rules in Sharing Animations</AlertTitle>
-When sharing animations, keep in mind that an asset ID can only be used between the group or individual that owns the animation.
+Animations are restricted assets. For more information, see [Asset privacy](../../projects/assets/privacy.md).
 </Alert>
 
-**Exporting Animations**
+**Exporting animations**
 
 Make sure to save your animation before exporting it.
 

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

@@ -1,6 +1,6 @@
 ---
 title: Experiences and places
-description: Explains how to publish the places in your experience.
+description: Explains how to create, publish, and configure experiences.
 ---
 
 <figure>
@@ -225,6 +225,19 @@ To release your experience to the public:
 
 1. <Chip label="RECOMMENDED" size="small" variant="outlined" color="success" /> Generate [Content maturity and compliance](#generate-content-descriptors) information so the experience is available to the appropriate audience. If you do not do this step, Roblox does not show your experience to players under 13 years old.
 
+### Set age and geography restrictions
+
+You can set restrictions so that only players over a certain age or from specific regions can play and discover your experiences. This is particularly helpful when you want to age up your audience without including mature content to age gate through content maturity labels.
+
+To set age and geography restrictions:
+
+1. Navigate to the [Creator Dashboard][creatordashboard].
+1. Click on the thumbnail of the experience for which you want to set age and geography restriction. The experience's **Overview** page displays.
+1. In the left-hand navigation, navigate to **Audience** > **Access Settings**.
+1. In the **Age** section, set **Minimum age** to the youngest age a player can have to access your experience.
+1. In the **Region** section, enable every region that can access your experience.
+1. At the bottom of the page, click the **Save Changes** button.
+
 ### Copy landing page link
 
 After you publish your experience, Roblox generates a landing page for the experience referred to as the experience's **main details page**. You can access and copy this link from either the [Creator Dashboard][creatordashboard] or the Roblox app, then share it with others so they can play your experience.
@@ -265,7 +278,7 @@ For step-by-step instructions on how to edit collaborator permissions, see [Role
 Roblox automatically retains saved versions of each place for version control and backup purposes. To access and revert to a previously saved version of any place within an experience:
 
 1. Navigate to the [Creator Dashboard][creatordashboard] and click on the thumbnail of the experience. The experience's **Overview** page displays.
-1. In the left-hand navigation, under **Configure**, select **Places**.
+1. In the left-hand navigation, navigate to **Configure** > **Places**.
 1. On the **Places** page, click the thumbnail of the place you'd like to revert to a previous version.
 1. In the left-hand navigation, click **Version History**.
 1. Locate and select the version to revert to, then click the **Restore** button. Confirm the action to restore to that version.
@@ -281,15 +294,15 @@ By default, all private and public experiences are locked so that you or your [g
 To allow the community to access an editable copy of your experience:
 
 1. Navigate to the [Creator Dashboard][creatordashboard].
-2. Click on the thumbnail of the experience you want to allow players to copy. The experience's **Overview** page displays.
-3. In the left-hand navigation, navigate to **Configure** > **Places**.
-4. Click the **start place** marked with a star icon. The place's **Basic Settings** page displays.
+1. Click on the thumbnail of the experience you want to allow players to copy. The experience's **Overview** page displays.
+1. In the left-hand navigation, navigate to **Configure** > **Places**.
+1. Click the **start place** marked with a star icon. The place's **Basic Settings** page displays.
 
    <img src="../../assets/creator-dashboard/Places-Start-Place-Icon.png" width="200" alt="Start place tile indicated in Places display on the Creator Dashboard" />
 
-5. In the place's left-hand navigation menu, select **Permissions**.
-6. Enable **Allow users to download a copy of this Place**.
-7. Click the **Save Changes** button. Your experience is now uncopylocked and creators can access an editable copy of it from the experience's main page by clicking the **&ctdot;** button and selecting **Edit in Studio**.
+1. In the place's left-hand navigation menu, select **Permissions**.
+1. Enable **Allow users to download a copy of this Place**.
+1. Click the **Save Changes** button. Your experience is now uncopylocked and creators can access an editable copy of it from the experience's main page by clicking the **&ctdot;** button and selecting **Edit in Studio**.
 
    <img src="../../assets/publishing/experiences-places-assets/Edit-Place-In-Studio.jpg" width="780" />
 

content/en-us/projects/experience-ownership-transfer.md

@@ -10,54 +10,7 @@ With **experience ownership transfer**, you can transfer your experiences to [gr
 Before making a transfer or accepting a transfer, you must first:
 
 - Verify your email address.
-- Upload your private `Class.ModuleScript|ModuleScripts` to the group you're transferring the experience to. If the experience uses packages where the package owner is a user and not a group, you might have to recreate those packages or replace them with packages that are already owned by a group.
-- Publish your animation assets to the group you're transferring the experience to.
-
-  - If you have a large number of animations to upload, you can use a community-supported third-party tool like [Roblox Animation Transfer](https://github.com/evaera/roblox-animation-transfer). See [Transfer animations](./transfer-animations.md) for more details.
-  - If you have a small number of animations to upload, you can manually re-upload them and then update your animation asset references to support old and new IDs based on the `CreatorID` and `CreatorType`. See the following code for an example:
-
-  ```lua
-  -- Maps animation IDs that belong to the original creator to animation IDs
-  -- that belong to the new creator.
-  local transferAnimationMap = {
-  	["6406676108"] = 14292200298,
-  	["6438293322"] = 14292082312,
-  	["6464978998"] = 14292224322,
-  	["6465240715"] = 14292226967,
-  	["6465244287"] = 14292229476,
-  	["6382318344"] = 14292213468,
-  	["6382564692"] = 14292207171,
-  	["6460651769"] = 14292098870,
-  	["6415507655"] = 14292218236,
-  	["6415509331"] = 14292221034
-  }
-
-  function mapTransferAnimationId(id)
-
-  	-- If experience has been transferred, maps old animation IDs to new
-  	if game:GetService("RunService"):IsStudio() or
-  	(game.CreatorType == Enum.CreatorType.Group and
-  		game.CreatorId == 32626384) then
-  			local animationId = string.match(id, "%d+$")
-  			local mappedId = transferAnimationMap[animationId]
-
-  			if mappedId then
-  				return "rbxassetid://" .. mappedId
-  			end
-  	end
-
-  	return id
-  end
-
-  -- Creates an animation instance associated with the
-  -- specified rbxassetid://<animation_id>
-  function createAnimation(id)
-  	local animation = Instance.new("Animation")
-  	animation.AnimationId = mapTransferAnimationId(id)
-
-  	return animation
-  end
-  ```
+- Upload your private `Class.ModuleScript|ModuleScripts` and `Class.InsertService|InsertService` asset usages to the group you're transferring the experience to. If the experience uses packages where the package owner is a user and not a group, you might have to recreate those packages or replace them with packages that are already owned by a group.
 
 <Alert severity="info">
 As a best practice, if you're using Open Cloud API keys for the experience, create an API key as the new owner with the name `RobloxTransferApiKey`. During the transfer, the relevant scopes are added to this new key and removed from the original key. You can then use a feature flag to allow your backend services to start using the new key after the transfer is complete.