update Open Source Docs from Roblox internal teams

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

content/en-us/cloud/guides/inventory.md

@@ -11,7 +11,7 @@ Responses from the [Inventory API][1] include items from the following categorie
 - Purchases and rewards (badges, passes, purchased places, private servers)
 - Avatar items (avatar animations, classic heads, emotes, faces, hair, heads)
 
-Before using the [Inventory API][1], you must [generate an API key](api-keys.md) or [configure OAuth 2](oauth2-overview.md) for your app. The examples on this page use API keys.
+Before using the [Inventory API][1], you must [generate an API key](../auth/api-keys.md) or [configure OAuth 2](../auth/oauth2-overview.md) for your app. The examples on this page use API keys.
 
 ## Check item ownership
 

content/en-us/cloud/guides/usage-assets.md

@@ -115,11 +115,11 @@ Updating asset metadata using the **Update Asset** endpoint is not subject to th
       </td>
       <td>
         <ul>
-          <li>Up to 30 seconds of duration.</li>
+          <li>Up to 60 seconds of duration.</li>
           <li>Up to 4096x2160 resolution.</li>
-          <li>Up to 375 MB.</li>
+          <li>Up to 750 MB.</li>
           <li>Currently, only English, Spanish, Portuguese, Indonesian, Chinese (simplified and traditional), Japanese, and/or Korean audio and text are allowed.</li>
-          <li>Up to 3 uploads per month if you're 13+ and ID-verified.</li>
+          <li>Up to 10 uploads per month if you're 13+ and ID-verified.</li>
         </ul>
       </td>
     </tr>
@@ -129,11 +129,11 @@ Updating asset metadata using the **Update Asset** endpoint is not subject to th
 
 ## Security permissions
 
-The API supports both first-party use with [API key authorization](./api-keys.md) and third-party use in [OAuth 2 applications](./oauth2-overview.md). Each way requires different security permission settings.
+The API supports both first-party use with [API key authorization](../auth/api-keys.md) and third-party use in [OAuth 2 applications](../auth/oauth2-overview.md). Each way requires different security permission settings.
 
 ### API keys
 
-To use the API in your own scripts or tools, you need to [create an API key](./api-keys.md#create-api-keys) for authorization and security. To manage assets that you own individually, create the API key under your account. To manage group-owned assets, create the API key under the target group. For more information on group-owned API keys, see [Group-owned API key permissions](./api-keys.md#group-owned-api-key-permissions).
+To use the API in your own scripts or tools, you need to [create an API key](../auth/api-keys.md#create-api-keys) for authorization and security. To manage assets that you own individually, create the API key under your account. To manage group-owned assets, create the API key under the target group. For more information on group-owned API keys, see [Group-owned API key permissions](../auth/api-keys.md#group-owned-api-key-permissions).
 
 Once you create an API key, you can't switch its ownership between individuals or groups, so if you create an API key under your own account, you can't use it for managing group assets.
 
@@ -154,7 +154,7 @@ Once you have the API key, copy it to the `x-api-key` request header. All endpoi
 
 ### OAuth 2.0 apps
 
-To use the API for a third-party OAuth 2.0 application, add the `asset:read` and `asset:write` permission scopes when [registering your app](./oauth2-registration.md#add-permissions). Choose these scopes based on the requirements of the endpoints you plan to use.
+To use the API for a third-party OAuth 2.0 application, add the `asset:read` and `asset:write` permission scopes when [registering your app](../auth/oauth2-registration.md#add-permissions). Choose these scopes based on the requirements of the endpoints you plan to use.
 
 ## Create a new asset
 
@@ -321,7 +321,7 @@ Third-Party app support through OAuth 2.0 is a Beta feature that might be subjec
 
 To use Assets API for your application and request permissions from your users, perform the following settings:
 
-1. When [registering your application](./oauth2-registration.md#register-an-app), under **Permissions**, select **asset:read** and **asset:write** scopes.
+1. When [registering your application](../auth/oauth2-registration.md#register-your-app), under **Permissions**, select **asset:read** and **asset:write** scopes.
 
 1. When [implementing the authorization flow](../../cloud/auth/oauth2-overview.md#implement-authorization-flows), include `asset:read` and `asset:write` as the scope parameters of the authorization URL that redirects users back to your application, like the following example:
 

content/en-us/cloud/guides/usage-messaging.md

@@ -57,7 +57,7 @@ Players.PlayerAdded:Connect(onPlayerAdded)
 
 After [setting up](#set-up-a-topic-for-messaging) a topic, publish a message to your experience's live servers:
 
-1. [Create an API key](./api-keys.md#creating-an-API-key) on [Creator Dashboard](https://create.roblox.com/dashboard/credentials) and copy it somewhere safe. Make sure you perform the following settings:
+1. [Create an API key](../auth/api-keys.md#create-api-keys) on [Creator Dashboard](https://create.roblox.com/dashboard/credentials) and copy it somewhere safe. Make sure you perform the following settings:
 
    1. Add **messaging-service** to **Access Permissions**.
    2. Select an experience, and add the **universe-messaging-service:publish** operation.
@@ -98,14 +98,14 @@ Third-party app support through OAuth 2.0 is a beta feature that might be subjec
 
 To use Messaging Service API for your application and request permissions from your users, perform the following settings:
 
-1. When [registering your application](./oauth2-registration.md#registering-an-app), under **Permissions**, select the **universe-messaging-service:publish** scope.
-2. When [implementing the authorization flow](../../cloud/auth/oauth2-overview.md#implementing-authorization-flows), include `universe-messaging-service:publish` in the `scope` parameter of the authorization URL that redirects users back to your application, like the following example:
+1. When [registering your application](../auth/oauth2-registration.md#register-your-app), under **Permissions**, select the **universe-messaging-service:publish** scope.
+2. When [implementing the authorization flow](../../cloud/auth/oauth2-overview.md), include `universe-messaging-service:publish` in the `scope` parameter of the authorization URL that redirects users back to your application, like the following example:
 
    ```plain
    https://authorize.roblox.com?client_id=816547628409595165403873012&redirect_uri=https://my-app.com/redirect&scope=openid+universe-messaging-service:publish&response_type=Code&prompts=login+consent&nonce=12345&state=6789
    ```
 
-3. Request access to the `universeId` of the experience that the user wants to publish their messages to. Your application can send a `POST` request to the [token resources endpoint](oauth2-reference.md#token-exchange) with the access token, client ID and secret or the `code challenge`, depending on your [implementation of your authorization flow](../../cloud/auth/oauth2-overview.md#implementing-authorization-flows), as request parameters to get a list of `universeIds` of experiences that the user granted permission to:
+3. Request access to the `universeId` of the experience that the user wants to publish their messages to. Your application can send a `POST` request to the [token resources endpoint](../auth/oauth2-reference.md#token-exchange) with the access token, client ID and secret or the `code challenge`, depending on your [implementation of your authorization flow](../../cloud/auth/oauth2-overview.md#implementing-authorization-flows), as request parameters to get a list of `universeIds` of experiences that the user granted permission to:
 
    ```bash title="Example Request"
    curl --location --request POST 'https://apis.roblox.com/oauth/v1/token/resources' \

content/en-us/ui/video-frames.md

@@ -17,15 +17,15 @@ To upload video assets, you must be a 13+ [ID verified](https://en.help.roblox.c
 
 - You have the legal rights to use the video asset.
 - It adheres to the [Roblox Community Standards](https://en.help.roblox.com/hc/en-us/articles/203313410) and [Terms of Use](https://en.help.roblox.com/hc/en-us/articles/115004647846).
-- It's 30 seconds or less in either `.mp4` or `.mov` format.
+- It's 60 seconds or less in either `.mp4` or `.mov` format.
 - Its resolution is less than or equal to 4096×2160.
-- It's less than 375 MB.
+- It's less than 750 MB.
 - It includes only English, Spanish, Portuguese, Indonesian, Chinese (simplified and traditional), Japanese, and/or Korean audio and text.
 
 Videos that don't meet these requirements are rejected. Alpha channels are not supported and will be ignored. When uploading videos, consider the following:
 
 - Each video upload costs 2,000 Robux.
-- You can upload a maximum of three videos within any 30-day period, starting from the date of your first video upload.
+- You can upload a maximum of ten videos within any 30-day period, starting from the date of your first video upload.
 
 ### Upload