diff --git a/descriptions-next/ghec/dereferenced/ghec.2022-11-28.deref.json b/descriptions-next/ghec/dereferenced/ghec.2022-11-28.deref.json
index a3d789779..82d20be72 100644
--- a/descriptions-next/ghec/dereferenced/ghec.2022-11-28.deref.json
+++ b/descriptions-next/ghec/dereferenced/ghec.2022-11-28.deref.json
@@ -510559,7 +510559,7 @@
     "/scim/v2/enterprises/{enterprise}/Groups": {
       "get": {
         "summary": "List provisioned SCIM groups for an enterprise",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nLists provisioned SCIM groups in an enterprise.\n\nYou can improve query search time by using the `excludedAttributes` query parameter with a value of `members` to exclude members from the response.",
+        "description": "Lists provisioned SCIM groups in an enterprise.\n\nYou can improve query search time by using the `excludedAttributes` query parameter with a value of `members` to exclude members from the response.",
         "operationId": "enterprise-admin/list-provisioned-groups-enterprise",
         "tags": [
           "enterprise-admin",
@@ -511174,7 +511174,7 @@
       },
       "post": {
         "summary": "Provision a SCIM enterprise group",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nCreates a SCIM group for an enterprise.\n\nWhen members are part of the group provisioning payload, they're designated as external group members. Providers are responsible for maintaining a mapping between the `externalId` and `id` for each user.",
+        "description": "Creates a SCIM group for an enterprise.\n\nWhen members are part of the group provisioning payload, they're designated as external group members. Providers are responsible for maintaining a mapping between the `externalId` and `id` for each user.",
         "operationId": "enterprise-admin/provision-enterprise-group",
         "tags": [
           "enterprise-admin"
@@ -511759,7 +511759,7 @@
     "/scim/v2/enterprises/{enterprise}/Groups/{scim_group_id}": {
       "get": {
         "summary": "Get SCIM provisioning information for an enterprise group",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nGets information about a SCIM group.",
+        "description": "Gets information about a SCIM group.",
         "operationId": "enterprise-admin/get-provisioning-information-for-enterprise-group",
         "tags": [
           "enterprise-admin"
@@ -512306,7 +512306,7 @@
       },
       "put": {
         "summary": "Set SCIM information for a provisioned enterprise group",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nReplaces an existing provisioned group’s information.\n\nYou must provide all the information required for the group as if you were provisioning it for the first time. Any existing group information that you don't provide will be removed, including group membership. If you want to only update a specific attribute, use the [Update an attribute for a SCIM enterprise group](#update-an-attribute-for-a-scim-enterprise-group) endpoint instead.",
+        "description": "Replaces an existing provisioned group’s information.\n\nYou must provide all the information required for the group as if you were provisioning it for the first time. Any existing group information that you don't provide will be removed, including group membership. If you want to only update a specific attribute, use the [Update an attribute for a SCIM enterprise group](#update-an-attribute-for-a-scim-enterprise-group) endpoint instead.",
         "operationId": "enterprise-admin/set-information-for-provisioned-enterprise-group",
         "tags": [
           "enterprise-admin"
@@ -512976,7 +512976,7 @@
       },
       "patch": {
         "summary": "Update an attribute for a SCIM enterprise group",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nUpdate a provisioned group’s individual attributes.\n\nTo modify a group's values, you'll need to use a specific Operations JSON format which must include at least one of the following operations: add, remove, or replace. For examples and more information on this SCIM format, consult the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2). The update function can also be used to add group memberships.\n\nYou can submit group memberships individually or in batches for improved efficiency.\n\n> [!NOTE]\n> Memberships are referenced via a local user id. Ensure users are created before referencing them here.",
+        "description": "Update a provisioned group’s individual attributes.\n\nTo modify a group's values, you'll need to use a specific Operations JSON format which must include at least one of the following operations: add, remove, or replace. For examples and more information on this SCIM format, consult the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2). The update function can also be used to add group memberships.\n\nYou can submit group memberships individually or in batches for improved efficiency.\n\n> [!NOTE]\n> Memberships are referenced via a local user id. Ensure users are created before referencing them here.",
         "operationId": "enterprise-admin/update-attribute-for-enterprise-group",
         "tags": [
           "enterprise-admin"
@@ -513636,7 +513636,7 @@
       },
       "delete": {
         "summary": "Delete a SCIM group from an enterprise",
-        "description": "> [!NOTE]\n> SCIM provisioning using the REST API is in public preview and subject to change.\n\nDeletes a SCIM group from an enterprise.",
+        "description": "Deletes a SCIM group from an enterprise.",
         "operationId": "enterprise-admin/delete-scim-group-from-enterprise",
         "tags": [
           "enterprise-admin"
@@ -513983,7 +513983,7 @@
     "/scim/v2/enterprises/{enterprise}/Users": {
       "get": {
         "summary": "List SCIM provisioned identities for an enterprise",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nLists provisioned SCIM enterprise members.\n\nWhen you remove a user with a SCIM-provisioned external identity from an enterprise using a `patch` with `active` flag to `false`, the user's metadata remains intact. This means they can potentially re-join the enterprise later. Although, while suspended, the user can't sign in. If you want to ensure the user can't re-join in the future, use the delete request. Only users who weren't permanently deleted will appear in the result list.",
+        "description": "Lists provisioned SCIM enterprise members.\n\nWhen you remove a user with a SCIM-provisioned external identity from an enterprise using a `patch` with `active` flag to `false`, the user's metadata remains intact. This means they can potentially re-join the enterprise later. Although, while suspended, the user can't sign in. If you want to ensure the user can't re-join in the future, use the delete request. Only users who weren't permanently deleted will appear in the result list.",
         "operationId": "enterprise-admin/list-provisioned-identities-enterprise",
         "tags": [
           "enterprise-admin"
@@ -514675,7 +514675,7 @@
       },
       "post": {
         "summary": "Provision a SCIM enterprise user",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nCreates an external identity for a new SCIM enterprise user.\n\nSCIM is responsible for user provisioning, not authentication. The actual user authentication is handled by SAML. However, with SCIM enabled, users must first be provisioned via SCIM before they can sign in through SAML.",
+        "description": "Creates an external identity for a new SCIM enterprise user.\n\nSCIM is responsible for user provisioning, not authentication. The actual user authentication is handled by SAML. However, with SCIM enabled, users must first be provisioned via SCIM before they can sign in through SAML.",
         "operationId": "enterprise-admin/provision-enterprise-user",
         "tags": [
           "enterprise-admin"
@@ -515551,7 +515551,7 @@
     "/scim/v2/enterprises/{enterprise}/Users/{scim_user_id}": {
       "get": {
         "summary": "Get SCIM provisioning information for an enterprise user",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nGets information about a SCIM user.",
+        "description": "Gets information about a SCIM user.",
         "operationId": "enterprise-admin/get-provisioning-information-for-enterprise-user",
         "tags": [
           "enterprise-admin"
@@ -516179,7 +516179,7 @@
       },
       "put": {
         "summary": "Set SCIM information for a provisioned enterprise user",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nReplaces an existing provisioned user's information.\n\nYou must supply complete user information, just as you would when provisioning them initially. Any previously existing data not provided will be deleted. To update only a specific attribute, refer to the [Update an attribute for a SCIM user](#update-an-attribute-for-a-scim-enterprise-user) endpoint.\n\n> [!WARNING]\n> Setting `active: false` will suspend a user, and their handle and email will be obfuscated.",
+        "description": "Replaces an existing provisioned user's information.\n\nYou must supply complete user information, just as you would when provisioning them initially. Any previously existing data not provided will be deleted. To update only a specific attribute, refer to the [Update an attribute for a SCIM user](#update-an-attribute-for-a-scim-enterprise-user) endpoint.\n\n> [!WARNING]\n> Setting `active: false` will suspend a user, and their handle and email will be obfuscated.",
         "operationId": "enterprise-admin/set-information-for-provisioned-enterprise-user",
         "tags": [
           "enterprise-admin"
@@ -517020,7 +517020,7 @@
       },
       "patch": {
         "summary": "Update an attribute for a SCIM enterprise user",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nUpdate a provisioned user's individual attributes.\n\nTo modify a user's attributes, you'll need to provide a `Operations` JSON formatted request that includes at least one of the following actions: add, remove, or replace. For specific examples and more information on the SCIM operations format, please refer to the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2).\n\n> [!NOTE]\n> Complex SCIM `path` selectors that include filters are not supported. For example, a `path` selector defined as `\"path\": \"emails[type eq \\\"work\\\"]\"` will be ineffective.\n\n> [!WARNING]\n> Setting `active: false` will suspend a user, and their handle and email will be obfuscated.\n> ```\n> {\n>   \"Operations\":[{\n>     \"op\":\"replace\",\n>     \"value\":{\n>       \"active\":false\n>     }\n>   }]\n> }\n> ```",
+        "description": "Update a provisioned user's individual attributes.\n\nTo modify a user's attributes, you'll need to provide a `Operations` JSON formatted request that includes at least one of the following actions: add, remove, or replace. For specific examples and more information on the SCIM operations format, please refer to the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2).\n\n> [!NOTE]\n> Complex SCIM `path` selectors that include filters are not supported. For example, a `path` selector defined as `\"path\": \"emails[type eq \\\"work\\\"]\"` will be ineffective.\n\n> [!WARNING]\n> Setting `active: false` will suspend a user, and their handle and email will be obfuscated.\n> ```\n> {\n>   \"Operations\":[{\n>     \"op\":\"replace\",\n>     \"value\":{\n>       \"active\":false\n>     }\n>   }]\n> }\n> ```",
         "operationId": "enterprise-admin/update-attribute-for-enterprise-user",
         "tags": [
           "enterprise-admin"
@@ -517834,7 +517834,7 @@
       },
       "delete": {
         "summary": "Delete a SCIM user from an enterprise",
-        "description": "> [!NOTE]\n> SCIM provisioning using the REST API is in public preview and subject to change.\n\nSuspends a SCIM user permanently from an enterprise. This action will: remove all the user's data,  anonymize their login, email, and display name, erase all external identity SCIM attributes, delete the user's emails, avatar, PATs, SSH keys, OAuth authorizations, GPG keys, and SAML mappings. This action is irreversible.",
+        "description": "Suspends a SCIM user permanently from an enterprise. This action will: remove all the user's data,  anonymize their login, email, and display name, erase all external identity SCIM attributes, delete the user's emails, avatar, PATs, SSH keys, OAuth authorizations, GPG keys, and SAML mappings. This action is irreversible.",
         "operationId": "enterprise-admin/delete-user-from-enterprise",
         "tags": [
           "enterprise-admin"
diff --git a/descriptions-next/ghec/dereferenced/ghec.2022-11-28.deref.yaml b/descriptions-next/ghec/dereferenced/ghec.2022-11-28.deref.yaml
index 098c96d76..7c8bc3fe4 100644
--- a/descriptions-next/ghec/dereferenced/ghec.2022-11-28.deref.yaml
+++ b/descriptions-next/ghec/dereferenced/ghec.2022-11-28.deref.yaml
@@ -91120,9 +91120,6 @@ paths:
     get:
       summary: List provisioned SCIM groups for an enterprise
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Lists provisioned SCIM groups in an enterprise.
 
         You can improve query search time by using the `excludedAttributes` query parameter with a value of `members` to exclude members from the response.
@@ -91393,9 +91390,6 @@ paths:
     post:
       summary: Provision a SCIM enterprise group
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Creates a SCIM group for an enterprise.
 
         When members are part of the group provisioning payload, they're designated as external group members. Providers are responsible for maintaining a mapping between the `externalId` and `id` for each user.
@@ -91507,11 +91501,7 @@ paths:
   "/scim/v2/enterprises/{enterprise}/Groups/{scim_group_id}":
     get:
       summary: Get SCIM provisioning information for an enterprise group
-      description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
-        Gets information about a SCIM group.
+      description: Gets information about a SCIM group.
       operationId: enterprise-admin/get-provisioning-information-for-enterprise-group
       tags:
       - enterprise-admin
@@ -91552,9 +91542,6 @@ paths:
     put:
       summary: Set SCIM information for a provisioned enterprise group
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Replaces an existing provisioned group’s information.
 
         You must provide all the information required for the group as if you were provisioning it for the first time. Any existing group information that you don't provide will be removed, including group membership. If you want to only update a specific attribute, use the [Update an attribute for a SCIM enterprise group](#update-an-attribute-for-a-scim-enterprise-group) endpoint instead.
@@ -91616,9 +91603,6 @@ paths:
     patch:
       summary: Update an attribute for a SCIM enterprise group
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Update a provisioned group’s individual attributes.
 
         To modify a group's values, you'll need to use a specific Operations JSON format which must include at least one of the following operations: add, remove, or replace. For examples and more information on this SCIM format, consult the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2). The update function can also be used to add group memberships.
@@ -91718,11 +91702,7 @@ paths:
         subcategory: scim
     delete:
       summary: Delete a SCIM group from an enterprise
-      description: |-
-        > [!NOTE]
-        > SCIM provisioning using the REST API is in public preview and subject to change.
-
-        Deletes a SCIM group from an enterprise.
+      description: Deletes a SCIM group from an enterprise.
       operationId: enterprise-admin/delete-scim-group-from-enterprise
       tags:
       - enterprise-admin
@@ -91750,9 +91730,6 @@ paths:
     get:
       summary: List SCIM provisioned identities for an enterprise
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Lists provisioned SCIM enterprise members.
 
         When you remove a user with a SCIM-provisioned external identity from an enterprise using a `patch` with `active` flag to `false`, the user's metadata remains intact. This means they can potentially re-join the enterprise later. Although, while suspended, the user can't sign in. If you want to ensure the user can't re-join in the future, use the delete request. Only users who weren't permanently deleted will appear in the result list.
@@ -92015,9 +91992,6 @@ paths:
     post:
       summary: Provision a SCIM enterprise user
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Creates an external identity for a new SCIM enterprise user.
 
         SCIM is responsible for user provisioning, not authentication. The actual user authentication is handled by SAML. However, with SCIM enabled, users must first be provisioned via SCIM before they can sign in through SAML.
@@ -92218,11 +92192,7 @@ paths:
   "/scim/v2/enterprises/{enterprise}/Users/{scim_user_id}":
     get:
       summary: Get SCIM provisioning information for an enterprise user
-      description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
-        Gets information about a SCIM user.
+      description: Gets information about a SCIM user.
       operationId: enterprise-admin/get-provisioning-information-for-enterprise-user
       tags:
       - enterprise-admin
@@ -92260,9 +92230,6 @@ paths:
     put:
       summary: Set SCIM information for a provisioned enterprise user
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Replaces an existing provisioned user's information.
 
         You must supply complete user information, just as you would when provisioning them initially. Any previously existing data not provided will be deleted. To update only a specific attribute, refer to the [Update an attribute for a SCIM user](#update-an-attribute-for-a-scim-enterprise-user) endpoint.
@@ -92308,9 +92275,6 @@ paths:
     patch:
       summary: Update an attribute for a SCIM enterprise user
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Update a provisioned user's individual attributes.
 
         To modify a user's attributes, you'll need to provide a `Operations` JSON formatted request that includes at least one of the following actions: add, remove, or replace. For specific examples and more information on the SCIM operations format, please refer to the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2).
@@ -92402,11 +92366,11 @@ paths:
         subcategory: scim
     delete:
       summary: Delete a SCIM user from an enterprise
-      description: |-
-        > [!NOTE]
-        > SCIM provisioning using the REST API is in public preview and subject to change.
-
-        Suspends a SCIM user permanently from an enterprise. This action will: remove all the user's data,  anonymize their login, email, and display name, erase all external identity SCIM attributes, delete the user's emails, avatar, PATs, SSH keys, OAuth authorizations, GPG keys, and SAML mappings. This action is irreversible.
+      description: 'Suspends a SCIM user permanently from an enterprise. This action
+        will: remove all the user''s data,  anonymize their login, email, and display
+        name, erase all external identity SCIM attributes, delete the user''s emails,
+        avatar, PATs, SSH keys, OAuth authorizations, GPG keys, and SAML mappings.
+        This action is irreversible.'
       operationId: enterprise-admin/delete-user-from-enterprise
       tags:
       - enterprise-admin
diff --git a/descriptions-next/ghec/dereferenced/ghec.deref.json b/descriptions-next/ghec/dereferenced/ghec.deref.json
index a3d789779..82d20be72 100644
--- a/descriptions-next/ghec/dereferenced/ghec.deref.json
+++ b/descriptions-next/ghec/dereferenced/ghec.deref.json
@@ -510559,7 +510559,7 @@
     "/scim/v2/enterprises/{enterprise}/Groups": {
       "get": {
         "summary": "List provisioned SCIM groups for an enterprise",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nLists provisioned SCIM groups in an enterprise.\n\nYou can improve query search time by using the `excludedAttributes` query parameter with a value of `members` to exclude members from the response.",
+        "description": "Lists provisioned SCIM groups in an enterprise.\n\nYou can improve query search time by using the `excludedAttributes` query parameter with a value of `members` to exclude members from the response.",
         "operationId": "enterprise-admin/list-provisioned-groups-enterprise",
         "tags": [
           "enterprise-admin",
@@ -511174,7 +511174,7 @@
       },
       "post": {
         "summary": "Provision a SCIM enterprise group",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nCreates a SCIM group for an enterprise.\n\nWhen members are part of the group provisioning payload, they're designated as external group members. Providers are responsible for maintaining a mapping between the `externalId` and `id` for each user.",
+        "description": "Creates a SCIM group for an enterprise.\n\nWhen members are part of the group provisioning payload, they're designated as external group members. Providers are responsible for maintaining a mapping between the `externalId` and `id` for each user.",
         "operationId": "enterprise-admin/provision-enterprise-group",
         "tags": [
           "enterprise-admin"
@@ -511759,7 +511759,7 @@
     "/scim/v2/enterprises/{enterprise}/Groups/{scim_group_id}": {
       "get": {
         "summary": "Get SCIM provisioning information for an enterprise group",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nGets information about a SCIM group.",
+        "description": "Gets information about a SCIM group.",
         "operationId": "enterprise-admin/get-provisioning-information-for-enterprise-group",
         "tags": [
           "enterprise-admin"
@@ -512306,7 +512306,7 @@
       },
       "put": {
         "summary": "Set SCIM information for a provisioned enterprise group",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nReplaces an existing provisioned group’s information.\n\nYou must provide all the information required for the group as if you were provisioning it for the first time. Any existing group information that you don't provide will be removed, including group membership. If you want to only update a specific attribute, use the [Update an attribute for a SCIM enterprise group](#update-an-attribute-for-a-scim-enterprise-group) endpoint instead.",
+        "description": "Replaces an existing provisioned group’s information.\n\nYou must provide all the information required for the group as if you were provisioning it for the first time. Any existing group information that you don't provide will be removed, including group membership. If you want to only update a specific attribute, use the [Update an attribute for a SCIM enterprise group](#update-an-attribute-for-a-scim-enterprise-group) endpoint instead.",
         "operationId": "enterprise-admin/set-information-for-provisioned-enterprise-group",
         "tags": [
           "enterprise-admin"
@@ -512976,7 +512976,7 @@
       },
       "patch": {
         "summary": "Update an attribute for a SCIM enterprise group",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nUpdate a provisioned group’s individual attributes.\n\nTo modify a group's values, you'll need to use a specific Operations JSON format which must include at least one of the following operations: add, remove, or replace. For examples and more information on this SCIM format, consult the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2). The update function can also be used to add group memberships.\n\nYou can submit group memberships individually or in batches for improved efficiency.\n\n> [!NOTE]\n> Memberships are referenced via a local user id. Ensure users are created before referencing them here.",
+        "description": "Update a provisioned group’s individual attributes.\n\nTo modify a group's values, you'll need to use a specific Operations JSON format which must include at least one of the following operations: add, remove, or replace. For examples and more information on this SCIM format, consult the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2). The update function can also be used to add group memberships.\n\nYou can submit group memberships individually or in batches for improved efficiency.\n\n> [!NOTE]\n> Memberships are referenced via a local user id. Ensure users are created before referencing them here.",
         "operationId": "enterprise-admin/update-attribute-for-enterprise-group",
         "tags": [
           "enterprise-admin"
@@ -513636,7 +513636,7 @@
       },
       "delete": {
         "summary": "Delete a SCIM group from an enterprise",
-        "description": "> [!NOTE]\n> SCIM provisioning using the REST API is in public preview and subject to change.\n\nDeletes a SCIM group from an enterprise.",
+        "description": "Deletes a SCIM group from an enterprise.",
         "operationId": "enterprise-admin/delete-scim-group-from-enterprise",
         "tags": [
           "enterprise-admin"
@@ -513983,7 +513983,7 @@
     "/scim/v2/enterprises/{enterprise}/Users": {
       "get": {
         "summary": "List SCIM provisioned identities for an enterprise",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nLists provisioned SCIM enterprise members.\n\nWhen you remove a user with a SCIM-provisioned external identity from an enterprise using a `patch` with `active` flag to `false`, the user's metadata remains intact. This means they can potentially re-join the enterprise later. Although, while suspended, the user can't sign in. If you want to ensure the user can't re-join in the future, use the delete request. Only users who weren't permanently deleted will appear in the result list.",
+        "description": "Lists provisioned SCIM enterprise members.\n\nWhen you remove a user with a SCIM-provisioned external identity from an enterprise using a `patch` with `active` flag to `false`, the user's metadata remains intact. This means they can potentially re-join the enterprise later. Although, while suspended, the user can't sign in. If you want to ensure the user can't re-join in the future, use the delete request. Only users who weren't permanently deleted will appear in the result list.",
         "operationId": "enterprise-admin/list-provisioned-identities-enterprise",
         "tags": [
           "enterprise-admin"
@@ -514675,7 +514675,7 @@
       },
       "post": {
         "summary": "Provision a SCIM enterprise user",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nCreates an external identity for a new SCIM enterprise user.\n\nSCIM is responsible for user provisioning, not authentication. The actual user authentication is handled by SAML. However, with SCIM enabled, users must first be provisioned via SCIM before they can sign in through SAML.",
+        "description": "Creates an external identity for a new SCIM enterprise user.\n\nSCIM is responsible for user provisioning, not authentication. The actual user authentication is handled by SAML. However, with SCIM enabled, users must first be provisioned via SCIM before they can sign in through SAML.",
         "operationId": "enterprise-admin/provision-enterprise-user",
         "tags": [
           "enterprise-admin"
@@ -515551,7 +515551,7 @@
     "/scim/v2/enterprises/{enterprise}/Users/{scim_user_id}": {
       "get": {
         "summary": "Get SCIM provisioning information for an enterprise user",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nGets information about a SCIM user.",
+        "description": "Gets information about a SCIM user.",
         "operationId": "enterprise-admin/get-provisioning-information-for-enterprise-user",
         "tags": [
           "enterprise-admin"
@@ -516179,7 +516179,7 @@
       },
       "put": {
         "summary": "Set SCIM information for a provisioned enterprise user",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nReplaces an existing provisioned user's information.\n\nYou must supply complete user information, just as you would when provisioning them initially. Any previously existing data not provided will be deleted. To update only a specific attribute, refer to the [Update an attribute for a SCIM user](#update-an-attribute-for-a-scim-enterprise-user) endpoint.\n\n> [!WARNING]\n> Setting `active: false` will suspend a user, and their handle and email will be obfuscated.",
+        "description": "Replaces an existing provisioned user's information.\n\nYou must supply complete user information, just as you would when provisioning them initially. Any previously existing data not provided will be deleted. To update only a specific attribute, refer to the [Update an attribute for a SCIM user](#update-an-attribute-for-a-scim-enterprise-user) endpoint.\n\n> [!WARNING]\n> Setting `active: false` will suspend a user, and their handle and email will be obfuscated.",
         "operationId": "enterprise-admin/set-information-for-provisioned-enterprise-user",
         "tags": [
           "enterprise-admin"
@@ -517020,7 +517020,7 @@
       },
       "patch": {
         "summary": "Update an attribute for a SCIM enterprise user",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nUpdate a provisioned user's individual attributes.\n\nTo modify a user's attributes, you'll need to provide a `Operations` JSON formatted request that includes at least one of the following actions: add, remove, or replace. For specific examples and more information on the SCIM operations format, please refer to the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2).\n\n> [!NOTE]\n> Complex SCIM `path` selectors that include filters are not supported. For example, a `path` selector defined as `\"path\": \"emails[type eq \\\"work\\\"]\"` will be ineffective.\n\n> [!WARNING]\n> Setting `active: false` will suspend a user, and their handle and email will be obfuscated.\n> ```\n> {\n>   \"Operations\":[{\n>     \"op\":\"replace\",\n>     \"value\":{\n>       \"active\":false\n>     }\n>   }]\n> }\n> ```",
+        "description": "Update a provisioned user's individual attributes.\n\nTo modify a user's attributes, you'll need to provide a `Operations` JSON formatted request that includes at least one of the following actions: add, remove, or replace. For specific examples and more information on the SCIM operations format, please refer to the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2).\n\n> [!NOTE]\n> Complex SCIM `path` selectors that include filters are not supported. For example, a `path` selector defined as `\"path\": \"emails[type eq \\\"work\\\"]\"` will be ineffective.\n\n> [!WARNING]\n> Setting `active: false` will suspend a user, and their handle and email will be obfuscated.\n> ```\n> {\n>   \"Operations\":[{\n>     \"op\":\"replace\",\n>     \"value\":{\n>       \"active\":false\n>     }\n>   }]\n> }\n> ```",
         "operationId": "enterprise-admin/update-attribute-for-enterprise-user",
         "tags": [
           "enterprise-admin"
@@ -517834,7 +517834,7 @@
       },
       "delete": {
         "summary": "Delete a SCIM user from an enterprise",
-        "description": "> [!NOTE]\n> SCIM provisioning using the REST API is in public preview and subject to change.\n\nSuspends a SCIM user permanently from an enterprise. This action will: remove all the user's data,  anonymize their login, email, and display name, erase all external identity SCIM attributes, delete the user's emails, avatar, PATs, SSH keys, OAuth authorizations, GPG keys, and SAML mappings. This action is irreversible.",
+        "description": "Suspends a SCIM user permanently from an enterprise. This action will: remove all the user's data,  anonymize their login, email, and display name, erase all external identity SCIM attributes, delete the user's emails, avatar, PATs, SSH keys, OAuth authorizations, GPG keys, and SAML mappings. This action is irreversible.",
         "operationId": "enterprise-admin/delete-user-from-enterprise",
         "tags": [
           "enterprise-admin"
diff --git a/descriptions-next/ghec/dereferenced/ghec.deref.yaml b/descriptions-next/ghec/dereferenced/ghec.deref.yaml
index 098c96d76..7c8bc3fe4 100644
--- a/descriptions-next/ghec/dereferenced/ghec.deref.yaml
+++ b/descriptions-next/ghec/dereferenced/ghec.deref.yaml
@@ -91120,9 +91120,6 @@ paths:
     get:
       summary: List provisioned SCIM groups for an enterprise
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Lists provisioned SCIM groups in an enterprise.
 
         You can improve query search time by using the `excludedAttributes` query parameter with a value of `members` to exclude members from the response.
@@ -91393,9 +91390,6 @@ paths:
     post:
       summary: Provision a SCIM enterprise group
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Creates a SCIM group for an enterprise.
 
         When members are part of the group provisioning payload, they're designated as external group members. Providers are responsible for maintaining a mapping between the `externalId` and `id` for each user.
@@ -91507,11 +91501,7 @@ paths:
   "/scim/v2/enterprises/{enterprise}/Groups/{scim_group_id}":
     get:
       summary: Get SCIM provisioning information for an enterprise group
-      description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
-        Gets information about a SCIM group.
+      description: Gets information about a SCIM group.
       operationId: enterprise-admin/get-provisioning-information-for-enterprise-group
       tags:
       - enterprise-admin
@@ -91552,9 +91542,6 @@ paths:
     put:
       summary: Set SCIM information for a provisioned enterprise group
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Replaces an existing provisioned group’s information.
 
         You must provide all the information required for the group as if you were provisioning it for the first time. Any existing group information that you don't provide will be removed, including group membership. If you want to only update a specific attribute, use the [Update an attribute for a SCIM enterprise group](#update-an-attribute-for-a-scim-enterprise-group) endpoint instead.
@@ -91616,9 +91603,6 @@ paths:
     patch:
       summary: Update an attribute for a SCIM enterprise group
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Update a provisioned group’s individual attributes.
 
         To modify a group's values, you'll need to use a specific Operations JSON format which must include at least one of the following operations: add, remove, or replace. For examples and more information on this SCIM format, consult the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2). The update function can also be used to add group memberships.
@@ -91718,11 +91702,7 @@ paths:
         subcategory: scim
     delete:
       summary: Delete a SCIM group from an enterprise
-      description: |-
-        > [!NOTE]
-        > SCIM provisioning using the REST API is in public preview and subject to change.
-
-        Deletes a SCIM group from an enterprise.
+      description: Deletes a SCIM group from an enterprise.
       operationId: enterprise-admin/delete-scim-group-from-enterprise
       tags:
       - enterprise-admin
@@ -91750,9 +91730,6 @@ paths:
     get:
       summary: List SCIM provisioned identities for an enterprise
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Lists provisioned SCIM enterprise members.
 
         When you remove a user with a SCIM-provisioned external identity from an enterprise using a `patch` with `active` flag to `false`, the user's metadata remains intact. This means they can potentially re-join the enterprise later. Although, while suspended, the user can't sign in. If you want to ensure the user can't re-join in the future, use the delete request. Only users who weren't permanently deleted will appear in the result list.
@@ -92015,9 +91992,6 @@ paths:
     post:
       summary: Provision a SCIM enterprise user
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Creates an external identity for a new SCIM enterprise user.
 
         SCIM is responsible for user provisioning, not authentication. The actual user authentication is handled by SAML. However, with SCIM enabled, users must first be provisioned via SCIM before they can sign in through SAML.
@@ -92218,11 +92192,7 @@ paths:
   "/scim/v2/enterprises/{enterprise}/Users/{scim_user_id}":
     get:
       summary: Get SCIM provisioning information for an enterprise user
-      description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
-        Gets information about a SCIM user.
+      description: Gets information about a SCIM user.
       operationId: enterprise-admin/get-provisioning-information-for-enterprise-user
       tags:
       - enterprise-admin
@@ -92260,9 +92230,6 @@ paths:
     put:
       summary: Set SCIM information for a provisioned enterprise user
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Replaces an existing provisioned user's information.
 
         You must supply complete user information, just as you would when provisioning them initially. Any previously existing data not provided will be deleted. To update only a specific attribute, refer to the [Update an attribute for a SCIM user](#update-an-attribute-for-a-scim-enterprise-user) endpoint.
@@ -92308,9 +92275,6 @@ paths:
     patch:
       summary: Update an attribute for a SCIM enterprise user
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Update a provisioned user's individual attributes.
 
         To modify a user's attributes, you'll need to provide a `Operations` JSON formatted request that includes at least one of the following actions: add, remove, or replace. For specific examples and more information on the SCIM operations format, please refer to the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2).
@@ -92402,11 +92366,11 @@ paths:
         subcategory: scim
     delete:
       summary: Delete a SCIM user from an enterprise
-      description: |-
-        > [!NOTE]
-        > SCIM provisioning using the REST API is in public preview and subject to change.
-
-        Suspends a SCIM user permanently from an enterprise. This action will: remove all the user's data,  anonymize their login, email, and display name, erase all external identity SCIM attributes, delete the user's emails, avatar, PATs, SSH keys, OAuth authorizations, GPG keys, and SAML mappings. This action is irreversible.
+      description: 'Suspends a SCIM user permanently from an enterprise. This action
+        will: remove all the user''s data,  anonymize their login, email, and display
+        name, erase all external identity SCIM attributes, delete the user''s emails,
+        avatar, PATs, SSH keys, OAuth authorizations, GPG keys, and SAML mappings.
+        This action is irreversible.'
       operationId: enterprise-admin/delete-user-from-enterprise
       tags:
       - enterprise-admin
diff --git a/descriptions-next/ghec/ghec.2022-11-28.json b/descriptions-next/ghec/ghec.2022-11-28.json
index 9bcaaabea..02386f525 100644
--- a/descriptions-next/ghec/ghec.2022-11-28.json
+++ b/descriptions-next/ghec/ghec.2022-11-28.json
@@ -61693,7 +61693,7 @@
     "/scim/v2/enterprises/{enterprise}/Groups": {
       "get": {
         "summary": "List provisioned SCIM groups for an enterprise",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nLists provisioned SCIM groups in an enterprise.\n\nYou can improve query search time by using the `excludedAttributes` query parameter with a value of `members` to exclude members from the response.",
+        "description": "Lists provisioned SCIM groups in an enterprise.\n\nYou can improve query search time by using the `excludedAttributes` query parameter with a value of `members` to exclude members from the response.",
         "operationId": "enterprise-admin/list-provisioned-groups-enterprise",
         "tags": [
           "enterprise-admin",
@@ -61775,7 +61775,7 @@
       },
       "post": {
         "summary": "Provision a SCIM enterprise group",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nCreates a SCIM group for an enterprise.\n\nWhen members are part of the group provisioning payload, they're designated as external group members. Providers are responsible for maintaining a mapping between the `externalId` and `id` for each user.",
+        "description": "Creates a SCIM group for an enterprise.\n\nWhen members are part of the group provisioning payload, they're designated as external group members. Providers are responsible for maintaining a mapping between the `externalId` and `id` for each user.",
         "operationId": "enterprise-admin/provision-enterprise-group",
         "tags": [
           "enterprise-admin"
@@ -61856,7 +61856,7 @@
     "/scim/v2/enterprises/{enterprise}/Groups/{scim_group_id}": {
       "get": {
         "summary": "Get SCIM provisioning information for an enterprise group",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nGets information about a SCIM group.",
+        "description": "Gets information about a SCIM group.",
         "operationId": "enterprise-admin/get-provisioning-information-for-enterprise-group",
         "tags": [
           "enterprise-admin"
@@ -61920,7 +61920,7 @@
       },
       "put": {
         "summary": "Set SCIM information for a provisioned enterprise group",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nReplaces an existing provisioned group’s information.\n\nYou must provide all the information required for the group as if you were provisioning it for the first time. Any existing group information that you don't provide will be removed, including group membership. If you want to only update a specific attribute, use the [Update an attribute for a SCIM enterprise group](#update-an-attribute-for-a-scim-enterprise-group) endpoint instead.",
+        "description": "Replaces an existing provisioned group’s information.\n\nYou must provide all the information required for the group as if you were provisioning it for the first time. Any existing group information that you don't provide will be removed, including group membership. If you want to only update a specific attribute, use the [Update an attribute for a SCIM enterprise group](#update-an-attribute-for-a-scim-enterprise-group) endpoint instead.",
         "operationId": "enterprise-admin/set-information-for-provisioned-enterprise-group",
         "tags": [
           "enterprise-admin"
@@ -62029,7 +62029,7 @@
       },
       "patch": {
         "summary": "Update an attribute for a SCIM enterprise group",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nUpdate a provisioned group’s individual attributes.\n\nTo modify a group's values, you'll need to use a specific Operations JSON format which must include at least one of the following operations: add, remove, or replace. For examples and more information on this SCIM format, consult the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2). The update function can also be used to add group memberships.\n\nYou can submit group memberships individually or in batches for improved efficiency.\n\n> [!NOTE]\n> Memberships are referenced via a local user id. Ensure users are created before referencing them here.",
+        "description": "Update a provisioned group’s individual attributes.\n\nTo modify a group's values, you'll need to use a specific Operations JSON format which must include at least one of the following operations: add, remove, or replace. For examples and more information on this SCIM format, consult the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2). The update function can also be used to add group memberships.\n\nYou can submit group memberships individually or in batches for improved efficiency.\n\n> [!NOTE]\n> Memberships are referenced via a local user id. Ensure users are created before referencing them here.",
         "operationId": "enterprise-admin/update-attribute-for-enterprise-group",
         "tags": [
           "enterprise-admin"
@@ -62148,7 +62148,7 @@
       },
       "delete": {
         "summary": "Delete a SCIM group from an enterprise",
-        "description": "> [!NOTE]\n> SCIM provisioning using the REST API is in public preview and subject to change.\n\nDeletes a SCIM group from an enterprise.",
+        "description": "Deletes a SCIM group from an enterprise.",
         "operationId": "enterprise-admin/delete-scim-group-from-enterprise",
         "tags": [
           "enterprise-admin"
@@ -62199,7 +62199,7 @@
     "/scim/v2/enterprises/{enterprise}/Users": {
       "get": {
         "summary": "List SCIM provisioned identities for an enterprise",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nLists provisioned SCIM enterprise members.\n\nWhen you remove a user with a SCIM-provisioned external identity from an enterprise using a `patch` with `active` flag to `false`, the user's metadata remains intact. This means they can potentially re-join the enterprise later. Although, while suspended, the user can't sign in. If you want to ensure the user can't re-join in the future, use the delete request. Only users who weren't permanently deleted will appear in the result list.",
+        "description": "Lists provisioned SCIM enterprise members.\n\nWhen you remove a user with a SCIM-provisioned external identity from an enterprise using a `patch` with `active` flag to `false`, the user's metadata remains intact. This means they can potentially re-join the enterprise later. Although, while suspended, the user can't sign in. If you want to ensure the user can't re-join in the future, use the delete request. Only users who weren't permanently deleted will appear in the result list.",
         "operationId": "enterprise-admin/list-provisioned-identities-enterprise",
         "tags": [
           "enterprise-admin"
@@ -62277,7 +62277,7 @@
       },
       "post": {
         "summary": "Provision a SCIM enterprise user",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nCreates an external identity for a new SCIM enterprise user.\n\nSCIM is responsible for user provisioning, not authentication. The actual user authentication is handled by SAML. However, with SCIM enabled, users must first be provisioned via SCIM before they can sign in through SAML.",
+        "description": "Creates an external identity for a new SCIM enterprise user.\n\nSCIM is responsible for user provisioning, not authentication. The actual user authentication is handled by SAML. However, with SCIM enabled, users must first be provisioned via SCIM before they can sign in through SAML.",
         "operationId": "enterprise-admin/provision-enterprise-user",
         "tags": [
           "enterprise-admin"
@@ -62358,7 +62358,7 @@
     "/scim/v2/enterprises/{enterprise}/Users/{scim_user_id}": {
       "get": {
         "summary": "Get SCIM provisioning information for an enterprise user",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nGets information about a SCIM user.",
+        "description": "Gets information about a SCIM user.",
         "operationId": "enterprise-admin/get-provisioning-information-for-enterprise-user",
         "tags": [
           "enterprise-admin"
@@ -62419,7 +62419,7 @@
       },
       "put": {
         "summary": "Set SCIM information for a provisioned enterprise user",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nReplaces an existing provisioned user's information.\n\nYou must supply complete user information, just as you would when provisioning them initially. Any previously existing data not provided will be deleted. To update only a specific attribute, refer to the [Update an attribute for a SCIM user](#update-an-attribute-for-a-scim-enterprise-user) endpoint.\n\n> [!WARNING]\n> Setting `active: false` will suspend a user, and their handle and email will be obfuscated.",
+        "description": "Replaces an existing provisioned user's information.\n\nYou must supply complete user information, just as you would when provisioning them initially. Any previously existing data not provided will be deleted. To update only a specific attribute, refer to the [Update an attribute for a SCIM user](#update-an-attribute-for-a-scim-enterprise-user) endpoint.\n\n> [!WARNING]\n> Setting `active: false` will suspend a user, and their handle and email will be obfuscated.",
         "operationId": "enterprise-admin/set-information-for-provisioned-enterprise-user",
         "tags": [
           "enterprise-admin"
@@ -62498,7 +62498,7 @@
       },
       "patch": {
         "summary": "Update an attribute for a SCIM enterprise user",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nUpdate a provisioned user's individual attributes.\n\nTo modify a user's attributes, you'll need to provide a `Operations` JSON formatted request that includes at least one of the following actions: add, remove, or replace. For specific examples and more information on the SCIM operations format, please refer to the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2).\n\n> [!NOTE]\n> Complex SCIM `path` selectors that include filters are not supported. For example, a `path` selector defined as `\"path\": \"emails[type eq \\\"work\\\"]\"` will be ineffective.\n\n> [!WARNING]\n> Setting `active: false` will suspend a user, and their handle and email will be obfuscated.\n> ```\n> {\n>   \"Operations\":[{\n>     \"op\":\"replace\",\n>     \"value\":{\n>       \"active\":false\n>     }\n>   }]\n> }\n> ```",
+        "description": "Update a provisioned user's individual attributes.\n\nTo modify a user's attributes, you'll need to provide a `Operations` JSON formatted request that includes at least one of the following actions: add, remove, or replace. For specific examples and more information on the SCIM operations format, please refer to the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2).\n\n> [!NOTE]\n> Complex SCIM `path` selectors that include filters are not supported. For example, a `path` selector defined as `\"path\": \"emails[type eq \\\"work\\\"]\"` will be ineffective.\n\n> [!WARNING]\n> Setting `active: false` will suspend a user, and their handle and email will be obfuscated.\n> ```\n> {\n>   \"Operations\":[{\n>     \"op\":\"replace\",\n>     \"value\":{\n>       \"active\":false\n>     }\n>   }]\n> }\n> ```",
         "operationId": "enterprise-admin/update-attribute-for-enterprise-user",
         "tags": [
           "enterprise-admin"
@@ -62635,7 +62635,7 @@
       },
       "delete": {
         "summary": "Delete a SCIM user from an enterprise",
-        "description": "> [!NOTE]\n> SCIM provisioning using the REST API is in public preview and subject to change.\n\nSuspends a SCIM user permanently from an enterprise. This action will: remove all the user's data,  anonymize their login, email, and display name, erase all external identity SCIM attributes, delete the user's emails, avatar, PATs, SSH keys, OAuth authorizations, GPG keys, and SAML mappings. This action is irreversible.",
+        "description": "Suspends a SCIM user permanently from an enterprise. This action will: remove all the user's data,  anonymize their login, email, and display name, erase all external identity SCIM attributes, delete the user's emails, avatar, PATs, SSH keys, OAuth authorizations, GPG keys, and SAML mappings. This action is irreversible.",
         "operationId": "enterprise-admin/delete-user-from-enterprise",
         "tags": [
           "enterprise-admin"
diff --git a/descriptions-next/ghec/ghec.2022-11-28.yaml b/descriptions-next/ghec/ghec.2022-11-28.yaml
index 58d02bf26..3999ac654 100644
--- a/descriptions-next/ghec/ghec.2022-11-28.yaml
+++ b/descriptions-next/ghec/ghec.2022-11-28.yaml
@@ -44669,9 +44669,6 @@ paths:
     get:
       summary: List provisioned SCIM groups for an enterprise
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Lists provisioned SCIM groups in an enterprise.
 
         You can improve query search time by using the `excludedAttributes` query parameter with a value of `members` to exclude members from the response.
@@ -44728,9 +44725,6 @@ paths:
     post:
       summary: Provision a SCIM enterprise group
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Creates a SCIM group for an enterprise.
 
         When members are part of the group provisioning payload, they're designated as external group members. Providers are responsible for maintaining a mapping between the `externalId` and `id` for each user.
@@ -44785,11 +44779,7 @@ paths:
   "/scim/v2/enterprises/{enterprise}/Groups/{scim_group_id}":
     get:
       summary: Get SCIM provisioning information for an enterprise group
-      description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
-        Gets information about a SCIM group.
+      description: Gets information about a SCIM group.
       operationId: enterprise-admin/get-provisioning-information-for-enterprise-group
       tags:
       - enterprise-admin
@@ -44830,9 +44820,6 @@ paths:
     put:
       summary: Set SCIM information for a provisioned enterprise group
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Replaces an existing provisioned group’s information.
 
         You must provide all the information required for the group as if you were provisioning it for the first time. Any existing group information that you don't provide will be removed, including group membership. If you want to only update a specific attribute, use the [Update an attribute for a SCIM enterprise group](#update-an-attribute-for-a-scim-enterprise-group) endpoint instead.
@@ -44905,9 +44892,6 @@ paths:
     patch:
       summary: Update an attribute for a SCIM enterprise group
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Update a provisioned group’s individual attributes.
 
         To modify a group's values, you'll need to use a specific Operations JSON format which must include at least one of the following operations: add, remove, or replace. For examples and more information on this SCIM format, consult the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2). The update function can also be used to add group memberships.
@@ -44987,11 +44971,7 @@ paths:
         subcategory: scim
     delete:
       summary: Delete a SCIM group from an enterprise
-      description: |-
-        > [!NOTE]
-        > SCIM provisioning using the REST API is in public preview and subject to change.
-
-        Deletes a SCIM group from an enterprise.
+      description: Deletes a SCIM group from an enterprise.
       operationId: enterprise-admin/delete-scim-group-from-enterprise
       tags:
       - enterprise-admin
@@ -45025,9 +45005,6 @@ paths:
     get:
       summary: List SCIM provisioned identities for an enterprise
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Lists provisioned SCIM enterprise members.
 
         When you remove a user with a SCIM-provisioned external identity from an enterprise using a `patch` with `active` flag to `false`, the user's metadata remains intact. This means they can potentially re-join the enterprise later. Although, while suspended, the user can't sign in. If you want to ensure the user can't re-join in the future, use the delete request. Only users who weren't permanently deleted will appear in the result list.
@@ -45083,9 +45060,6 @@ paths:
     post:
       summary: Provision a SCIM enterprise user
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Creates an external identity for a new SCIM enterprise user.
 
         SCIM is responsible for user provisioning, not authentication. The actual user authentication is handled by SAML. However, with SCIM enabled, users must first be provisioned via SCIM before they can sign in through SAML.
@@ -45140,11 +45114,7 @@ paths:
   "/scim/v2/enterprises/{enterprise}/Users/{scim_user_id}":
     get:
       summary: Get SCIM provisioning information for an enterprise user
-      description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
-        Gets information about a SCIM user.
+      description: Gets information about a SCIM user.
       operationId: enterprise-admin/get-provisioning-information-for-enterprise-user
       tags:
       - enterprise-admin
@@ -45184,9 +45154,6 @@ paths:
     put:
       summary: Set SCIM information for a provisioned enterprise user
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Replaces an existing provisioned user's information.
 
         You must supply complete user information, just as you would when provisioning them initially. Any previously existing data not provided will be deleted. To update only a specific attribute, refer to the [Update an attribute for a SCIM user](#update-an-attribute-for-a-scim-enterprise-user) endpoint.
@@ -45243,9 +45210,6 @@ paths:
     patch:
       summary: Update an attribute for a SCIM enterprise user
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Update a provisioned user's individual attributes.
 
         To modify a user's attributes, you'll need to provide a `Operations` JSON formatted request that includes at least one of the following actions: add, remove, or replace. For specific examples and more information on the SCIM operations format, please refer to the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2).
@@ -45349,11 +45313,11 @@ paths:
         subcategory: scim
     delete:
       summary: Delete a SCIM user from an enterprise
-      description: |-
-        > [!NOTE]
-        > SCIM provisioning using the REST API is in public preview and subject to change.
-
-        Suspends a SCIM user permanently from an enterprise. This action will: remove all the user's data,  anonymize their login, email, and display name, erase all external identity SCIM attributes, delete the user's emails, avatar, PATs, SSH keys, OAuth authorizations, GPG keys, and SAML mappings. This action is irreversible.
+      description: 'Suspends a SCIM user permanently from an enterprise. This action
+        will: remove all the user''s data,  anonymize their login, email, and display
+        name, erase all external identity SCIM attributes, delete the user''s emails,
+        avatar, PATs, SSH keys, OAuth authorizations, GPG keys, and SAML mappings.
+        This action is irreversible.'
       operationId: enterprise-admin/delete-user-from-enterprise
       tags:
       - enterprise-admin
diff --git a/descriptions-next/ghec/ghec.json b/descriptions-next/ghec/ghec.json
index 9bcaaabea..02386f525 100644
--- a/descriptions-next/ghec/ghec.json
+++ b/descriptions-next/ghec/ghec.json
@@ -61693,7 +61693,7 @@
     "/scim/v2/enterprises/{enterprise}/Groups": {
       "get": {
         "summary": "List provisioned SCIM groups for an enterprise",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nLists provisioned SCIM groups in an enterprise.\n\nYou can improve query search time by using the `excludedAttributes` query parameter with a value of `members` to exclude members from the response.",
+        "description": "Lists provisioned SCIM groups in an enterprise.\n\nYou can improve query search time by using the `excludedAttributes` query parameter with a value of `members` to exclude members from the response.",
         "operationId": "enterprise-admin/list-provisioned-groups-enterprise",
         "tags": [
           "enterprise-admin",
@@ -61775,7 +61775,7 @@
       },
       "post": {
         "summary": "Provision a SCIM enterprise group",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nCreates a SCIM group for an enterprise.\n\nWhen members are part of the group provisioning payload, they're designated as external group members. Providers are responsible for maintaining a mapping between the `externalId` and `id` for each user.",
+        "description": "Creates a SCIM group for an enterprise.\n\nWhen members are part of the group provisioning payload, they're designated as external group members. Providers are responsible for maintaining a mapping between the `externalId` and `id` for each user.",
         "operationId": "enterprise-admin/provision-enterprise-group",
         "tags": [
           "enterprise-admin"
@@ -61856,7 +61856,7 @@
     "/scim/v2/enterprises/{enterprise}/Groups/{scim_group_id}": {
       "get": {
         "summary": "Get SCIM provisioning information for an enterprise group",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nGets information about a SCIM group.",
+        "description": "Gets information about a SCIM group.",
         "operationId": "enterprise-admin/get-provisioning-information-for-enterprise-group",
         "tags": [
           "enterprise-admin"
@@ -61920,7 +61920,7 @@
       },
       "put": {
         "summary": "Set SCIM information for a provisioned enterprise group",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nReplaces an existing provisioned group’s information.\n\nYou must provide all the information required for the group as if you were provisioning it for the first time. Any existing group information that you don't provide will be removed, including group membership. If you want to only update a specific attribute, use the [Update an attribute for a SCIM enterprise group](#update-an-attribute-for-a-scim-enterprise-group) endpoint instead.",
+        "description": "Replaces an existing provisioned group’s information.\n\nYou must provide all the information required for the group as if you were provisioning it for the first time. Any existing group information that you don't provide will be removed, including group membership. If you want to only update a specific attribute, use the [Update an attribute for a SCIM enterprise group](#update-an-attribute-for-a-scim-enterprise-group) endpoint instead.",
         "operationId": "enterprise-admin/set-information-for-provisioned-enterprise-group",
         "tags": [
           "enterprise-admin"
@@ -62029,7 +62029,7 @@
       },
       "patch": {
         "summary": "Update an attribute for a SCIM enterprise group",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nUpdate a provisioned group’s individual attributes.\n\nTo modify a group's values, you'll need to use a specific Operations JSON format which must include at least one of the following operations: add, remove, or replace. For examples and more information on this SCIM format, consult the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2). The update function can also be used to add group memberships.\n\nYou can submit group memberships individually or in batches for improved efficiency.\n\n> [!NOTE]\n> Memberships are referenced via a local user id. Ensure users are created before referencing them here.",
+        "description": "Update a provisioned group’s individual attributes.\n\nTo modify a group's values, you'll need to use a specific Operations JSON format which must include at least one of the following operations: add, remove, or replace. For examples and more information on this SCIM format, consult the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2). The update function can also be used to add group memberships.\n\nYou can submit group memberships individually or in batches for improved efficiency.\n\n> [!NOTE]\n> Memberships are referenced via a local user id. Ensure users are created before referencing them here.",
         "operationId": "enterprise-admin/update-attribute-for-enterprise-group",
         "tags": [
           "enterprise-admin"
@@ -62148,7 +62148,7 @@
       },
       "delete": {
         "summary": "Delete a SCIM group from an enterprise",
-        "description": "> [!NOTE]\n> SCIM provisioning using the REST API is in public preview and subject to change.\n\nDeletes a SCIM group from an enterprise.",
+        "description": "Deletes a SCIM group from an enterprise.",
         "operationId": "enterprise-admin/delete-scim-group-from-enterprise",
         "tags": [
           "enterprise-admin"
@@ -62199,7 +62199,7 @@
     "/scim/v2/enterprises/{enterprise}/Users": {
       "get": {
         "summary": "List SCIM provisioned identities for an enterprise",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nLists provisioned SCIM enterprise members.\n\nWhen you remove a user with a SCIM-provisioned external identity from an enterprise using a `patch` with `active` flag to `false`, the user's metadata remains intact. This means they can potentially re-join the enterprise later. Although, while suspended, the user can't sign in. If you want to ensure the user can't re-join in the future, use the delete request. Only users who weren't permanently deleted will appear in the result list.",
+        "description": "Lists provisioned SCIM enterprise members.\n\nWhen you remove a user with a SCIM-provisioned external identity from an enterprise using a `patch` with `active` flag to `false`, the user's metadata remains intact. This means they can potentially re-join the enterprise later. Although, while suspended, the user can't sign in. If you want to ensure the user can't re-join in the future, use the delete request. Only users who weren't permanently deleted will appear in the result list.",
         "operationId": "enterprise-admin/list-provisioned-identities-enterprise",
         "tags": [
           "enterprise-admin"
@@ -62277,7 +62277,7 @@
       },
       "post": {
         "summary": "Provision a SCIM enterprise user",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nCreates an external identity for a new SCIM enterprise user.\n\nSCIM is responsible for user provisioning, not authentication. The actual user authentication is handled by SAML. However, with SCIM enabled, users must first be provisioned via SCIM before they can sign in through SAML.",
+        "description": "Creates an external identity for a new SCIM enterprise user.\n\nSCIM is responsible for user provisioning, not authentication. The actual user authentication is handled by SAML. However, with SCIM enabled, users must first be provisioned via SCIM before they can sign in through SAML.",
         "operationId": "enterprise-admin/provision-enterprise-user",
         "tags": [
           "enterprise-admin"
@@ -62358,7 +62358,7 @@
     "/scim/v2/enterprises/{enterprise}/Users/{scim_user_id}": {
       "get": {
         "summary": "Get SCIM provisioning information for an enterprise user",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nGets information about a SCIM user.",
+        "description": "Gets information about a SCIM user.",
         "operationId": "enterprise-admin/get-provisioning-information-for-enterprise-user",
         "tags": [
           "enterprise-admin"
@@ -62419,7 +62419,7 @@
       },
       "put": {
         "summary": "Set SCIM information for a provisioned enterprise user",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nReplaces an existing provisioned user's information.\n\nYou must supply complete user information, just as you would when provisioning them initially. Any previously existing data not provided will be deleted. To update only a specific attribute, refer to the [Update an attribute for a SCIM user](#update-an-attribute-for-a-scim-enterprise-user) endpoint.\n\n> [!WARNING]\n> Setting `active: false` will suspend a user, and their handle and email will be obfuscated.",
+        "description": "Replaces an existing provisioned user's information.\n\nYou must supply complete user information, just as you would when provisioning them initially. Any previously existing data not provided will be deleted. To update only a specific attribute, refer to the [Update an attribute for a SCIM user](#update-an-attribute-for-a-scim-enterprise-user) endpoint.\n\n> [!WARNING]\n> Setting `active: false` will suspend a user, and their handle and email will be obfuscated.",
         "operationId": "enterprise-admin/set-information-for-provisioned-enterprise-user",
         "tags": [
           "enterprise-admin"
@@ -62498,7 +62498,7 @@
       },
       "patch": {
         "summary": "Update an attribute for a SCIM enterprise user",
-        "description": "> [!NOTE]\n> SCIM provisioning for users and groups using the REST API is in public preview and subject to change.\n\nUpdate a provisioned user's individual attributes.\n\nTo modify a user's attributes, you'll need to provide a `Operations` JSON formatted request that includes at least one of the following actions: add, remove, or replace. For specific examples and more information on the SCIM operations format, please refer to the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2).\n\n> [!NOTE]\n> Complex SCIM `path` selectors that include filters are not supported. For example, a `path` selector defined as `\"path\": \"emails[type eq \\\"work\\\"]\"` will be ineffective.\n\n> [!WARNING]\n> Setting `active: false` will suspend a user, and their handle and email will be obfuscated.\n> ```\n> {\n>   \"Operations\":[{\n>     \"op\":\"replace\",\n>     \"value\":{\n>       \"active\":false\n>     }\n>   }]\n> }\n> ```",
+        "description": "Update a provisioned user's individual attributes.\n\nTo modify a user's attributes, you'll need to provide a `Operations` JSON formatted request that includes at least one of the following actions: add, remove, or replace. For specific examples and more information on the SCIM operations format, please refer to the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2).\n\n> [!NOTE]\n> Complex SCIM `path` selectors that include filters are not supported. For example, a `path` selector defined as `\"path\": \"emails[type eq \\\"work\\\"]\"` will be ineffective.\n\n> [!WARNING]\n> Setting `active: false` will suspend a user, and their handle and email will be obfuscated.\n> ```\n> {\n>   \"Operations\":[{\n>     \"op\":\"replace\",\n>     \"value\":{\n>       \"active\":false\n>     }\n>   }]\n> }\n> ```",
         "operationId": "enterprise-admin/update-attribute-for-enterprise-user",
         "tags": [
           "enterprise-admin"
@@ -62635,7 +62635,7 @@
       },
       "delete": {
         "summary": "Delete a SCIM user from an enterprise",
-        "description": "> [!NOTE]\n> SCIM provisioning using the REST API is in public preview and subject to change.\n\nSuspends a SCIM user permanently from an enterprise. This action will: remove all the user's data,  anonymize their login, email, and display name, erase all external identity SCIM attributes, delete the user's emails, avatar, PATs, SSH keys, OAuth authorizations, GPG keys, and SAML mappings. This action is irreversible.",
+        "description": "Suspends a SCIM user permanently from an enterprise. This action will: remove all the user's data,  anonymize their login, email, and display name, erase all external identity SCIM attributes, delete the user's emails, avatar, PATs, SSH keys, OAuth authorizations, GPG keys, and SAML mappings. This action is irreversible.",
         "operationId": "enterprise-admin/delete-user-from-enterprise",
         "tags": [
           "enterprise-admin"
diff --git a/descriptions-next/ghec/ghec.yaml b/descriptions-next/ghec/ghec.yaml
index 58d02bf26..3999ac654 100644
--- a/descriptions-next/ghec/ghec.yaml
+++ b/descriptions-next/ghec/ghec.yaml
@@ -44669,9 +44669,6 @@ paths:
     get:
       summary: List provisioned SCIM groups for an enterprise
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Lists provisioned SCIM groups in an enterprise.
 
         You can improve query search time by using the `excludedAttributes` query parameter with a value of `members` to exclude members from the response.
@@ -44728,9 +44725,6 @@ paths:
     post:
       summary: Provision a SCIM enterprise group
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Creates a SCIM group for an enterprise.
 
         When members are part of the group provisioning payload, they're designated as external group members. Providers are responsible for maintaining a mapping between the `externalId` and `id` for each user.
@@ -44785,11 +44779,7 @@ paths:
   "/scim/v2/enterprises/{enterprise}/Groups/{scim_group_id}":
     get:
       summary: Get SCIM provisioning information for an enterprise group
-      description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
-        Gets information about a SCIM group.
+      description: Gets information about a SCIM group.
       operationId: enterprise-admin/get-provisioning-information-for-enterprise-group
       tags:
       - enterprise-admin
@@ -44830,9 +44820,6 @@ paths:
     put:
       summary: Set SCIM information for a provisioned enterprise group
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Replaces an existing provisioned group’s information.
 
         You must provide all the information required for the group as if you were provisioning it for the first time. Any existing group information that you don't provide will be removed, including group membership. If you want to only update a specific attribute, use the [Update an attribute for a SCIM enterprise group](#update-an-attribute-for-a-scim-enterprise-group) endpoint instead.
@@ -44905,9 +44892,6 @@ paths:
     patch:
       summary: Update an attribute for a SCIM enterprise group
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Update a provisioned group’s individual attributes.
 
         To modify a group's values, you'll need to use a specific Operations JSON format which must include at least one of the following operations: add, remove, or replace. For examples and more information on this SCIM format, consult the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2). The update function can also be used to add group memberships.
@@ -44987,11 +44971,7 @@ paths:
         subcategory: scim
     delete:
       summary: Delete a SCIM group from an enterprise
-      description: |-
-        > [!NOTE]
-        > SCIM provisioning using the REST API is in public preview and subject to change.
-
-        Deletes a SCIM group from an enterprise.
+      description: Deletes a SCIM group from an enterprise.
       operationId: enterprise-admin/delete-scim-group-from-enterprise
       tags:
       - enterprise-admin
@@ -45025,9 +45005,6 @@ paths:
     get:
       summary: List SCIM provisioned identities for an enterprise
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Lists provisioned SCIM enterprise members.
 
         When you remove a user with a SCIM-provisioned external identity from an enterprise using a `patch` with `active` flag to `false`, the user's metadata remains intact. This means they can potentially re-join the enterprise later. Although, while suspended, the user can't sign in. If you want to ensure the user can't re-join in the future, use the delete request. Only users who weren't permanently deleted will appear in the result list.
@@ -45083,9 +45060,6 @@ paths:
     post:
       summary: Provision a SCIM enterprise user
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Creates an external identity for a new SCIM enterprise user.
 
         SCIM is responsible for user provisioning, not authentication. The actual user authentication is handled by SAML. However, with SCIM enabled, users must first be provisioned via SCIM before they can sign in through SAML.
@@ -45140,11 +45114,7 @@ paths:
   "/scim/v2/enterprises/{enterprise}/Users/{scim_user_id}":
     get:
       summary: Get SCIM provisioning information for an enterprise user
-      description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
-        Gets information about a SCIM user.
+      description: Gets information about a SCIM user.
       operationId: enterprise-admin/get-provisioning-information-for-enterprise-user
       tags:
       - enterprise-admin
@@ -45184,9 +45154,6 @@ paths:
     put:
       summary: Set SCIM information for a provisioned enterprise user
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Replaces an existing provisioned user's information.
 
         You must supply complete user information, just as you would when provisioning them initially. Any previously existing data not provided will be deleted. To update only a specific attribute, refer to the [Update an attribute for a SCIM user](#update-an-attribute-for-a-scim-enterprise-user) endpoint.
@@ -45243,9 +45210,6 @@ paths:
     patch:
       summary: Update an attribute for a SCIM enterprise user
       description: |-
-        > [!NOTE]
-        > SCIM provisioning for users and groups using the REST API is in public preview and subject to change.
-
         Update a provisioned user's individual attributes.
 
         To modify a user's attributes, you'll need to provide a `Operations` JSON formatted request that includes at least one of the following actions: add, remove, or replace. For specific examples and more information on the SCIM operations format, please refer to the [SCIM specification](https://tools.ietf.org/html/rfc7644#section-3.5.2).
@@ -45349,11 +45313,11 @@ paths:
         subcategory: scim
     delete:
       summary: Delete a SCIM user from an enterprise
-      description: |-
-        > [!NOTE]
-        > SCIM provisioning using the REST API is in public preview and subject to change.
-
-        Suspends a SCIM user permanently from an enterprise. This action will: remove all the user's data,  anonymize their login, email, and display name, erase all external identity SCIM attributes, delete the user's emails, avatar, PATs, SSH keys, OAuth authorizations, GPG keys, and SAML mappings. This action is irreversible.
+      description: 'Suspends a SCIM user permanently from an enterprise. This action
+        will: remove all the user''s data,  anonymize their login, email, and display
+        name, erase all external identity SCIM attributes, delete the user''s emails,
+        avatar, PATs, SSH keys, OAuth authorizations, GPG keys, and SAML mappings.
+        This action is irreversible.'
       operationId: enterprise-admin/delete-user-from-enterprise
       tags:
       - enterprise-admin
diff --git a/descriptions-next/ghes-3.12/dereferenced/ghes-3.12.2022-11-28.deref.json b/descriptions-next/ghes-3.12/dereferenced/ghes-3.12.2022-11-28.deref.json
index 360ea85a1..6bd90a701 100644
--- a/descriptions-next/ghes-3.12/dereferenced/ghes-3.12.2022-11-28.deref.json
+++ b/descriptions-next/ghes-3.12/dereferenced/ghes-3.12.2022-11-28.deref.json
@@ -68503,15 +68503,15 @@
     },
     "/manage/v1/config/init": {
       "post": {
-        "summary": "Initialize instance configuration with license upload",
-        "description": "When you boot a GitHub instance for the first time, you can use this endpoint to upload a license.\n\nNote that you afterwards need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) to start the actual configuration process.\n\nThis endpoint also sets the root site administrator password which is used to authenticate with the GHES Manage API and the Management Console.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
+        "summary": "Initialize instance configuration with license and password",
+        "description": "When you boot and set up a GitHub instance for the first time, you can use this endpoint to upload a license and set the initial root site administrator password.\n\n> [!IMPORTANT]\n> To start the configuration process and apply the license, you need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)\n\nThe root site administrator password provided when calling this endpoint is used to authenticate for all other endpoints in the GHES Manage API and the Management Console UI.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
         "operationId": "enterprise-admin/initialize-instance-configuration",
         "tags": [
           "enterprise-admin"
         ],
         "externalDocs": {
           "description": "API method documentation",
-          "url": "https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-upload"
+          "url": "https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-and-password"
         },
         "servers": [
           {
@@ -68554,7 +68554,7 @@
                 "default": {
                   "value": {
                     "license": "@enterprise.ghl",
-                    "password": "secret-password!"
+                    "password": "provide-password-here!"
                   }
                 }
               }
@@ -68749,7 +68749,7 @@
       },
       "put": {
         "summary": "Upload an enterprise license",
-        "description": "Uploads an enterprise license. This operation does not automatically activate the license.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
+        "description": "Uploads a new enterprise license. In order to apply it right away, use the `apply` query parameter.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
         "operationId": "enterprise-admin/license-upload",
         "tags": [
           "enterprise-admin"
diff --git a/descriptions-next/ghes-3.12/dereferenced/ghes-3.12.2022-11-28.deref.yaml b/descriptions-next/ghes-3.12/dereferenced/ghes-3.12.2022-11-28.deref.yaml
index 8829a8498..d28c8e58b 100644
--- a/descriptions-next/ghes-3.12/dereferenced/ghes-3.12.2022-11-28.deref.yaml
+++ b/descriptions-next/ghes-3.12/dereferenced/ghes-3.12.2022-11-28.deref.yaml
@@ -19011,13 +19011,14 @@ paths:
         subcategory: manage-ghes
   "/manage/v1/config/init":
     post:
-      summary: Initialize instance configuration with license upload
+      summary: Initialize instance configuration with license and password
       description: |-
-        When you boot a GitHub instance for the first time, you can use this endpoint to upload a license.
+        When you boot and set up a GitHub instance for the first time, you can use this endpoint to upload a license and set the initial root site administrator password.
 
-        Note that you afterwards need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) to start the actual configuration process.
+        > [!IMPORTANT]
+        > To start the configuration process and apply the license, you need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)
 
-        This endpoint also sets the root site administrator password which is used to authenticate with the GHES Manage API and the Management Console.
+        The root site administrator password provided when calling this endpoint is used to authenticate for all other endpoints in the GHES Manage API and the Management Console UI.
 
         > [!NOTE]
         > The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).
@@ -19026,7 +19027,7 @@ paths:
       - enterprise-admin
       externalDocs:
         description: API method documentation
-        url: https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-upload
+        url: https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-and-password
       servers:
       - url: "{protocol}://{hostname}"
         variables:
@@ -19057,7 +19058,7 @@ paths:
               default:
                 value:
                   license: "@enterprise.ghl"
-                  password: secret-password!
+                  password: provide-password-here!
       responses:
         '202':
           description: Response
@@ -19202,7 +19203,7 @@ paths:
     put:
       summary: Upload an enterprise license
       description: |-
-        Uploads an enterprise license. This operation does not automatically activate the license.
+        Uploads a new enterprise license. In order to apply it right away, use the `apply` query parameter.
 
         > [!NOTE]
         > The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).
diff --git a/descriptions-next/ghes-3.12/dereferenced/ghes-3.12.deref.json b/descriptions-next/ghes-3.12/dereferenced/ghes-3.12.deref.json
index 360ea85a1..6bd90a701 100644
--- a/descriptions-next/ghes-3.12/dereferenced/ghes-3.12.deref.json
+++ b/descriptions-next/ghes-3.12/dereferenced/ghes-3.12.deref.json
@@ -68503,15 +68503,15 @@
     },
     "/manage/v1/config/init": {
       "post": {
-        "summary": "Initialize instance configuration with license upload",
-        "description": "When you boot a GitHub instance for the first time, you can use this endpoint to upload a license.\n\nNote that you afterwards need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) to start the actual configuration process.\n\nThis endpoint also sets the root site administrator password which is used to authenticate with the GHES Manage API and the Management Console.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
+        "summary": "Initialize instance configuration with license and password",
+        "description": "When you boot and set up a GitHub instance for the first time, you can use this endpoint to upload a license and set the initial root site administrator password.\n\n> [!IMPORTANT]\n> To start the configuration process and apply the license, you need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)\n\nThe root site administrator password provided when calling this endpoint is used to authenticate for all other endpoints in the GHES Manage API and the Management Console UI.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
         "operationId": "enterprise-admin/initialize-instance-configuration",
         "tags": [
           "enterprise-admin"
         ],
         "externalDocs": {
           "description": "API method documentation",
-          "url": "https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-upload"
+          "url": "https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-and-password"
         },
         "servers": [
           {
@@ -68554,7 +68554,7 @@
                 "default": {
                   "value": {
                     "license": "@enterprise.ghl",
-                    "password": "secret-password!"
+                    "password": "provide-password-here!"
                   }
                 }
               }
@@ -68749,7 +68749,7 @@
       },
       "put": {
         "summary": "Upload an enterprise license",
-        "description": "Uploads an enterprise license. This operation does not automatically activate the license.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
+        "description": "Uploads a new enterprise license. In order to apply it right away, use the `apply` query parameter.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
         "operationId": "enterprise-admin/license-upload",
         "tags": [
           "enterprise-admin"
diff --git a/descriptions-next/ghes-3.12/dereferenced/ghes-3.12.deref.yaml b/descriptions-next/ghes-3.12/dereferenced/ghes-3.12.deref.yaml
index 8829a8498..d28c8e58b 100644
--- a/descriptions-next/ghes-3.12/dereferenced/ghes-3.12.deref.yaml
+++ b/descriptions-next/ghes-3.12/dereferenced/ghes-3.12.deref.yaml
@@ -19011,13 +19011,14 @@ paths:
         subcategory: manage-ghes
   "/manage/v1/config/init":
     post:
-      summary: Initialize instance configuration with license upload
+      summary: Initialize instance configuration with license and password
       description: |-
-        When you boot a GitHub instance for the first time, you can use this endpoint to upload a license.
+        When you boot and set up a GitHub instance for the first time, you can use this endpoint to upload a license and set the initial root site administrator password.
 
-        Note that you afterwards need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) to start the actual configuration process.
+        > [!IMPORTANT]
+        > To start the configuration process and apply the license, you need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)
 
-        This endpoint also sets the root site administrator password which is used to authenticate with the GHES Manage API and the Management Console.
+        The root site administrator password provided when calling this endpoint is used to authenticate for all other endpoints in the GHES Manage API and the Management Console UI.
 
         > [!NOTE]
         > The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).
@@ -19026,7 +19027,7 @@ paths:
       - enterprise-admin
       externalDocs:
         description: API method documentation
-        url: https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-upload
+        url: https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-and-password
       servers:
       - url: "{protocol}://{hostname}"
         variables:
@@ -19057,7 +19058,7 @@ paths:
               default:
                 value:
                   license: "@enterprise.ghl"
-                  password: secret-password!
+                  password: provide-password-here!
       responses:
         '202':
           description: Response
@@ -19202,7 +19203,7 @@ paths:
     put:
       summary: Upload an enterprise license
       description: |-
-        Uploads an enterprise license. This operation does not automatically activate the license.
+        Uploads a new enterprise license. In order to apply it right away, use the `apply` query parameter.
 
         > [!NOTE]
         > The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).
diff --git a/descriptions-next/ghes-3.12/ghes-3.12.2022-11-28.json b/descriptions-next/ghes-3.12/ghes-3.12.2022-11-28.json
index 021cd6caf..bf8b78d6d 100644
--- a/descriptions-next/ghes-3.12/ghes-3.12.2022-11-28.json
+++ b/descriptions-next/ghes-3.12/ghes-3.12.2022-11-28.json
@@ -10427,15 +10427,15 @@
     },
     "/manage/v1/config/init": {
       "post": {
-        "summary": "Initialize instance configuration with license upload",
-        "description": "When you boot a GitHub instance for the first time, you can use this endpoint to upload a license.\n\nNote that you afterwards need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) to start the actual configuration process.\n\nThis endpoint also sets the root site administrator password which is used to authenticate with the GHES Manage API and the Management Console.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
+        "summary": "Initialize instance configuration with license and password",
+        "description": "When you boot and set up a GitHub instance for the first time, you can use this endpoint to upload a license and set the initial root site administrator password.\n\n> [!IMPORTANT]\n> To start the configuration process and apply the license, you need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)\n\nThe root site administrator password provided when calling this endpoint is used to authenticate for all other endpoints in the GHES Manage API and the Management Console UI.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
         "operationId": "enterprise-admin/initialize-instance-configuration",
         "tags": [
           "enterprise-admin"
         ],
         "externalDocs": {
           "description": "API method documentation",
-          "url": "https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-upload"
+          "url": "https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-and-password"
         },
         "servers": [
           {
@@ -10463,7 +10463,7 @@
                 "default": {
                   "value": {
                     "license": "@enterprise.ghl",
-                    "password": "secret-password!"
+                    "password": "provide-password-here!"
                   }
                 }
               }
@@ -10551,7 +10551,7 @@
       },
       "put": {
         "summary": "Upload an enterprise license",
-        "description": "Uploads an enterprise license. This operation does not automatically activate the license.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
+        "description": "Uploads a new enterprise license. In order to apply it right away, use the `apply` query parameter.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
         "operationId": "enterprise-admin/license-upload",
         "tags": [
           "enterprise-admin"
diff --git a/descriptions-next/ghes-3.12/ghes-3.12.2022-11-28.yaml b/descriptions-next/ghes-3.12/ghes-3.12.2022-11-28.yaml
index 8f543d6f7..3a9600bd8 100644
--- a/descriptions-next/ghes-3.12/ghes-3.12.2022-11-28.yaml
+++ b/descriptions-next/ghes-3.12/ghes-3.12.2022-11-28.yaml
@@ -7300,13 +7300,14 @@ paths:
         subcategory: manage-ghes
   "/manage/v1/config/init":
     post:
-      summary: Initialize instance configuration with license upload
+      summary: Initialize instance configuration with license and password
       description: |-
-        When you boot a GitHub instance for the first time, you can use this endpoint to upload a license.
+        When you boot and set up a GitHub instance for the first time, you can use this endpoint to upload a license and set the initial root site administrator password.
 
-        Note that you afterwards need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) to start the actual configuration process.
+        > [!IMPORTANT]
+        > To start the configuration process and apply the license, you need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)
 
-        This endpoint also sets the root site administrator password which is used to authenticate with the GHES Manage API and the Management Console.
+        The root site administrator password provided when calling this endpoint is used to authenticate for all other endpoints in the GHES Manage API and the Management Console UI.
 
         > [!NOTE]
         > The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).
@@ -7315,7 +7316,7 @@ paths:
       - enterprise-admin
       externalDocs:
         description: API method documentation
-        url: https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-upload
+        url: https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-and-password
       servers:
       - url: "{protocol}://{hostname}"
         variables:
@@ -7335,7 +7336,7 @@ paths:
               default:
                 value:
                   license: "@enterprise.ghl"
-                  password: secret-password!
+                  password: provide-password-here!
       responses:
         '202':
           description: Response
@@ -7392,7 +7393,7 @@ paths:
     put:
       summary: Upload an enterprise license
       description: |-
-        Uploads an enterprise license. This operation does not automatically activate the license.
+        Uploads a new enterprise license. In order to apply it right away, use the `apply` query parameter.
 
         > [!NOTE]
         > The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).
diff --git a/descriptions-next/ghes-3.12/ghes-3.12.json b/descriptions-next/ghes-3.12/ghes-3.12.json
index 021cd6caf..bf8b78d6d 100644
--- a/descriptions-next/ghes-3.12/ghes-3.12.json
+++ b/descriptions-next/ghes-3.12/ghes-3.12.json
@@ -10427,15 +10427,15 @@
     },
     "/manage/v1/config/init": {
       "post": {
-        "summary": "Initialize instance configuration with license upload",
-        "description": "When you boot a GitHub instance for the first time, you can use this endpoint to upload a license.\n\nNote that you afterwards need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) to start the actual configuration process.\n\nThis endpoint also sets the root site administrator password which is used to authenticate with the GHES Manage API and the Management Console.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
+        "summary": "Initialize instance configuration with license and password",
+        "description": "When you boot and set up a GitHub instance for the first time, you can use this endpoint to upload a license and set the initial root site administrator password.\n\n> [!IMPORTANT]\n> To start the configuration process and apply the license, you need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)\n\nThe root site administrator password provided when calling this endpoint is used to authenticate for all other endpoints in the GHES Manage API and the Management Console UI.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
         "operationId": "enterprise-admin/initialize-instance-configuration",
         "tags": [
           "enterprise-admin"
         ],
         "externalDocs": {
           "description": "API method documentation",
-          "url": "https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-upload"
+          "url": "https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-and-password"
         },
         "servers": [
           {
@@ -10463,7 +10463,7 @@
                 "default": {
                   "value": {
                     "license": "@enterprise.ghl",
-                    "password": "secret-password!"
+                    "password": "provide-password-here!"
                   }
                 }
               }
@@ -10551,7 +10551,7 @@
       },
       "put": {
         "summary": "Upload an enterprise license",
-        "description": "Uploads an enterprise license. This operation does not automatically activate the license.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
+        "description": "Uploads a new enterprise license. In order to apply it right away, use the `apply` query parameter.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
         "operationId": "enterprise-admin/license-upload",
         "tags": [
           "enterprise-admin"
diff --git a/descriptions-next/ghes-3.12/ghes-3.12.yaml b/descriptions-next/ghes-3.12/ghes-3.12.yaml
index 8f543d6f7..3a9600bd8 100644
--- a/descriptions-next/ghes-3.12/ghes-3.12.yaml
+++ b/descriptions-next/ghes-3.12/ghes-3.12.yaml
@@ -7300,13 +7300,14 @@ paths:
         subcategory: manage-ghes
   "/manage/v1/config/init":
     post:
-      summary: Initialize instance configuration with license upload
+      summary: Initialize instance configuration with license and password
       description: |-
-        When you boot a GitHub instance for the first time, you can use this endpoint to upload a license.
+        When you boot and set up a GitHub instance for the first time, you can use this endpoint to upload a license and set the initial root site administrator password.
 
-        Note that you afterwards need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) to start the actual configuration process.
+        > [!IMPORTANT]
+        > To start the configuration process and apply the license, you need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)
 
-        This endpoint also sets the root site administrator password which is used to authenticate with the GHES Manage API and the Management Console.
+        The root site administrator password provided when calling this endpoint is used to authenticate for all other endpoints in the GHES Manage API and the Management Console UI.
 
         > [!NOTE]
         > The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).
@@ -7315,7 +7316,7 @@ paths:
       - enterprise-admin
       externalDocs:
         description: API method documentation
-        url: https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-upload
+        url: https://docs.github.com/enterprise-server@3.12/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-and-password
       servers:
       - url: "{protocol}://{hostname}"
         variables:
@@ -7335,7 +7336,7 @@ paths:
               default:
                 value:
                   license: "@enterprise.ghl"
-                  password: secret-password!
+                  password: provide-password-here!
       responses:
         '202':
           description: Response
@@ -7392,7 +7393,7 @@ paths:
     put:
       summary: Upload an enterprise license
       description: |-
-        Uploads an enterprise license. This operation does not automatically activate the license.
+        Uploads a new enterprise license. In order to apply it right away, use the `apply` query parameter.
 
         > [!NOTE]
         > The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).
diff --git a/descriptions-next/ghes-3.13/dereferenced/ghes-3.13.2022-11-28.deref.json b/descriptions-next/ghes-3.13/dereferenced/ghes-3.13.2022-11-28.deref.json
index 2fdd764dc..806a9da8f 100644
--- a/descriptions-next/ghes-3.13/dereferenced/ghes-3.13.2022-11-28.deref.json
+++ b/descriptions-next/ghes-3.13/dereferenced/ghes-3.13.2022-11-28.deref.json
@@ -68642,15 +68642,15 @@
     },
     "/manage/v1/config/init": {
       "post": {
-        "summary": "Initialize instance configuration with license upload",
-        "description": "When you boot a GitHub instance for the first time, you can use this endpoint to upload a license.\n\nNote that you afterwards need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) to start the actual configuration process.\n\nThis endpoint also sets the root site administrator password which is used to authenticate with the GHES Manage API and the Management Console.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
+        "summary": "Initialize instance configuration with license and password",
+        "description": "When you boot and set up a GitHub instance for the first time, you can use this endpoint to upload a license and set the initial root site administrator password.\n\n> [!IMPORTANT]\n> To start the configuration process and apply the license, you need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)\n\nThe root site administrator password provided when calling this endpoint is used to authenticate for all other endpoints in the GHES Manage API and the Management Console UI.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
         "operationId": "enterprise-admin/initialize-instance-configuration",
         "tags": [
           "enterprise-admin"
         ],
         "externalDocs": {
           "description": "API method documentation",
-          "url": "https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-upload"
+          "url": "https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-and-password"
         },
         "servers": [
           {
@@ -68693,7 +68693,7 @@
                 "default": {
                   "value": {
                     "license": "@enterprise.ghl",
-                    "password": "secret-password!"
+                    "password": "provide-password-here!"
                   }
                 }
               }
@@ -68888,7 +68888,7 @@
       },
       "put": {
         "summary": "Upload an enterprise license",
-        "description": "Uploads an enterprise license. This operation does not automatically activate the license.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
+        "description": "Uploads a new enterprise license. In order to apply it right away, use the `apply` query parameter.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
         "operationId": "enterprise-admin/license-upload",
         "tags": [
           "enterprise-admin"
@@ -68915,7 +68915,7 @@
         "parameters": [
           {
             "name": "apply",
-            "description": "Whether to apply changes from the license. Uploading a license does not automatically apply changes. To make the changes effective, you can specify to apply the license too.",
+            "description": "Whether to instantly apply changes from the license. Otherwise the new license can be applied using the [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) endpoint.",
             "in": "query",
             "required": false,
             "schema": {
diff --git a/descriptions-next/ghes-3.13/dereferenced/ghes-3.13.2022-11-28.deref.yaml b/descriptions-next/ghes-3.13/dereferenced/ghes-3.13.2022-11-28.deref.yaml
index b5cfe7e02..85a12c673 100644
--- a/descriptions-next/ghes-3.13/dereferenced/ghes-3.13.2022-11-28.deref.yaml
+++ b/descriptions-next/ghes-3.13/dereferenced/ghes-3.13.2022-11-28.deref.yaml
@@ -19025,13 +19025,14 @@ paths:
         subcategory: manage-ghes
   "/manage/v1/config/init":
     post:
-      summary: Initialize instance configuration with license upload
+      summary: Initialize instance configuration with license and password
       description: |-
-        When you boot a GitHub instance for the first time, you can use this endpoint to upload a license.
+        When you boot and set up a GitHub instance for the first time, you can use this endpoint to upload a license and set the initial root site administrator password.
 
-        Note that you afterwards need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) to start the actual configuration process.
+        > [!IMPORTANT]
+        > To start the configuration process and apply the license, you need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)
 
-        This endpoint also sets the root site administrator password which is used to authenticate with the GHES Manage API and the Management Console.
+        The root site administrator password provided when calling this endpoint is used to authenticate for all other endpoints in the GHES Manage API and the Management Console UI.
 
         > [!NOTE]
         > The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).
@@ -19040,7 +19041,7 @@ paths:
       - enterprise-admin
       externalDocs:
         description: API method documentation
-        url: https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-upload
+        url: https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-and-password
       servers:
       - url: "{protocol}://{hostname}"
         variables:
@@ -19071,7 +19072,7 @@ paths:
               default:
                 value:
                   license: "@enterprise.ghl"
-                  password: secret-password!
+                  password: provide-password-here!
       responses:
         '202':
           description: Response
@@ -19216,7 +19217,7 @@ paths:
     put:
       summary: Upload an enterprise license
       description: |-
-        Uploads an enterprise license. This operation does not automatically activate the license.
+        Uploads a new enterprise license. In order to apply it right away, use the `apply` query parameter.
 
         > [!NOTE]
         > The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).
@@ -19237,9 +19238,9 @@ paths:
             description: Self-hosted Enterprise Server protocol
       parameters:
       - name: apply
-        description: Whether to apply changes from the license. Uploading a license
-          does not automatically apply changes. To make the changes effective, you
-          can specify to apply the license too.
+        description: Whether to instantly apply changes from the license. Otherwise
+          the new license can be applied using the [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)
+          endpoint.
         in: query
         required: false
         schema:
diff --git a/descriptions-next/ghes-3.13/dereferenced/ghes-3.13.deref.json b/descriptions-next/ghes-3.13/dereferenced/ghes-3.13.deref.json
index 2fdd764dc..806a9da8f 100644
--- a/descriptions-next/ghes-3.13/dereferenced/ghes-3.13.deref.json
+++ b/descriptions-next/ghes-3.13/dereferenced/ghes-3.13.deref.json
@@ -68642,15 +68642,15 @@
     },
     "/manage/v1/config/init": {
       "post": {
-        "summary": "Initialize instance configuration with license upload",
-        "description": "When you boot a GitHub instance for the first time, you can use this endpoint to upload a license.\n\nNote that you afterwards need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) to start the actual configuration process.\n\nThis endpoint also sets the root site administrator password which is used to authenticate with the GHES Manage API and the Management Console.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
+        "summary": "Initialize instance configuration with license and password",
+        "description": "When you boot and set up a GitHub instance for the first time, you can use this endpoint to upload a license and set the initial root site administrator password.\n\n> [!IMPORTANT]\n> To start the configuration process and apply the license, you need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)\n\nThe root site administrator password provided when calling this endpoint is used to authenticate for all other endpoints in the GHES Manage API and the Management Console UI.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
         "operationId": "enterprise-admin/initialize-instance-configuration",
         "tags": [
           "enterprise-admin"
         ],
         "externalDocs": {
           "description": "API method documentation",
-          "url": "https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-upload"
+          "url": "https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-and-password"
         },
         "servers": [
           {
@@ -68693,7 +68693,7 @@
                 "default": {
                   "value": {
                     "license": "@enterprise.ghl",
-                    "password": "secret-password!"
+                    "password": "provide-password-here!"
                   }
                 }
               }
@@ -68888,7 +68888,7 @@
       },
       "put": {
         "summary": "Upload an enterprise license",
-        "description": "Uploads an enterprise license. This operation does not automatically activate the license.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
+        "description": "Uploads a new enterprise license. In order to apply it right away, use the `apply` query parameter.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
         "operationId": "enterprise-admin/license-upload",
         "tags": [
           "enterprise-admin"
@@ -68915,7 +68915,7 @@
         "parameters": [
           {
             "name": "apply",
-            "description": "Whether to apply changes from the license. Uploading a license does not automatically apply changes. To make the changes effective, you can specify to apply the license too.",
+            "description": "Whether to instantly apply changes from the license. Otherwise the new license can be applied using the [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) endpoint.",
             "in": "query",
             "required": false,
             "schema": {
diff --git a/descriptions-next/ghes-3.13/dereferenced/ghes-3.13.deref.yaml b/descriptions-next/ghes-3.13/dereferenced/ghes-3.13.deref.yaml
index b5cfe7e02..85a12c673 100644
--- a/descriptions-next/ghes-3.13/dereferenced/ghes-3.13.deref.yaml
+++ b/descriptions-next/ghes-3.13/dereferenced/ghes-3.13.deref.yaml
@@ -19025,13 +19025,14 @@ paths:
         subcategory: manage-ghes
   "/manage/v1/config/init":
     post:
-      summary: Initialize instance configuration with license upload
+      summary: Initialize instance configuration with license and password
       description: |-
-        When you boot a GitHub instance for the first time, you can use this endpoint to upload a license.
+        When you boot and set up a GitHub instance for the first time, you can use this endpoint to upload a license and set the initial root site administrator password.
 
-        Note that you afterwards need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) to start the actual configuration process.
+        > [!IMPORTANT]
+        > To start the configuration process and apply the license, you need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)
 
-        This endpoint also sets the root site administrator password which is used to authenticate with the GHES Manage API and the Management Console.
+        The root site administrator password provided when calling this endpoint is used to authenticate for all other endpoints in the GHES Manage API and the Management Console UI.
 
         > [!NOTE]
         > The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).
@@ -19040,7 +19041,7 @@ paths:
       - enterprise-admin
       externalDocs:
         description: API method documentation
-        url: https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-upload
+        url: https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-and-password
       servers:
       - url: "{protocol}://{hostname}"
         variables:
@@ -19071,7 +19072,7 @@ paths:
               default:
                 value:
                   license: "@enterprise.ghl"
-                  password: secret-password!
+                  password: provide-password-here!
       responses:
         '202':
           description: Response
@@ -19216,7 +19217,7 @@ paths:
     put:
       summary: Upload an enterprise license
       description: |-
-        Uploads an enterprise license. This operation does not automatically activate the license.
+        Uploads a new enterprise license. In order to apply it right away, use the `apply` query parameter.
 
         > [!NOTE]
         > The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).
@@ -19237,9 +19238,9 @@ paths:
             description: Self-hosted Enterprise Server protocol
       parameters:
       - name: apply
-        description: Whether to apply changes from the license. Uploading a license
-          does not automatically apply changes. To make the changes effective, you
-          can specify to apply the license too.
+        description: Whether to instantly apply changes from the license. Otherwise
+          the new license can be applied using the [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)
+          endpoint.
         in: query
         required: false
         schema:
diff --git a/descriptions-next/ghes-3.13/ghes-3.13.2022-11-28.json b/descriptions-next/ghes-3.13/ghes-3.13.2022-11-28.json
index 156dbbdca..31548169f 100644
--- a/descriptions-next/ghes-3.13/ghes-3.13.2022-11-28.json
+++ b/descriptions-next/ghes-3.13/ghes-3.13.2022-11-28.json
@@ -10429,15 +10429,15 @@
     },
     "/manage/v1/config/init": {
       "post": {
-        "summary": "Initialize instance configuration with license upload",
-        "description": "When you boot a GitHub instance for the first time, you can use this endpoint to upload a license.\n\nNote that you afterwards need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) to start the actual configuration process.\n\nThis endpoint also sets the root site administrator password which is used to authenticate with the GHES Manage API and the Management Console.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
+        "summary": "Initialize instance configuration with license and password",
+        "description": "When you boot and set up a GitHub instance for the first time, you can use this endpoint to upload a license and set the initial root site administrator password.\n\n> [!IMPORTANT]\n> To start the configuration process and apply the license, you need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)\n\nThe root site administrator password provided when calling this endpoint is used to authenticate for all other endpoints in the GHES Manage API and the Management Console UI.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
         "operationId": "enterprise-admin/initialize-instance-configuration",
         "tags": [
           "enterprise-admin"
         ],
         "externalDocs": {
           "description": "API method documentation",
-          "url": "https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-upload"
+          "url": "https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-and-password"
         },
         "servers": [
           {
@@ -10465,7 +10465,7 @@
                 "default": {
                   "value": {
                     "license": "@enterprise.ghl",
-                    "password": "secret-password!"
+                    "password": "provide-password-here!"
                   }
                 }
               }
@@ -10553,7 +10553,7 @@
       },
       "put": {
         "summary": "Upload an enterprise license",
-        "description": "Uploads an enterprise license. This operation does not automatically activate the license.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
+        "description": "Uploads a new enterprise license. In order to apply it right away, use the `apply` query parameter.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
         "operationId": "enterprise-admin/license-upload",
         "tags": [
           "enterprise-admin"
@@ -288402,7 +288402,7 @@
       },
       "license-apply": {
         "name": "apply",
-        "description": "Whether to apply changes from the license. Uploading a license does not automatically apply changes. To make the changes effective, you can specify to apply the license too.",
+        "description": "Whether to instantly apply changes from the license. Otherwise the new license can be applied using the [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) endpoint.",
         "in": "query",
         "required": false,
         "schema": {
diff --git a/descriptions-next/ghes-3.13/ghes-3.13.2022-11-28.yaml b/descriptions-next/ghes-3.13/ghes-3.13.2022-11-28.yaml
index 86d96ad28..5214390b1 100644
--- a/descriptions-next/ghes-3.13/ghes-3.13.2022-11-28.yaml
+++ b/descriptions-next/ghes-3.13/ghes-3.13.2022-11-28.yaml
@@ -7304,13 +7304,14 @@ paths:
         subcategory: manage-ghes
   "/manage/v1/config/init":
     post:
-      summary: Initialize instance configuration with license upload
+      summary: Initialize instance configuration with license and password
       description: |-
-        When you boot a GitHub instance for the first time, you can use this endpoint to upload a license.
+        When you boot and set up a GitHub instance for the first time, you can use this endpoint to upload a license and set the initial root site administrator password.
 
-        Note that you afterwards need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) to start the actual configuration process.
+        > [!IMPORTANT]
+        > To start the configuration process and apply the license, you need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)
 
-        This endpoint also sets the root site administrator password which is used to authenticate with the GHES Manage API and the Management Console.
+        The root site administrator password provided when calling this endpoint is used to authenticate for all other endpoints in the GHES Manage API and the Management Console UI.
 
         > [!NOTE]
         > The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).
@@ -7319,7 +7320,7 @@ paths:
       - enterprise-admin
       externalDocs:
         description: API method documentation
-        url: https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-upload
+        url: https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-and-password
       servers:
       - url: "{protocol}://{hostname}"
         variables:
@@ -7339,7 +7340,7 @@ paths:
               default:
                 value:
                   license: "@enterprise.ghl"
-                  password: secret-password!
+                  password: provide-password-here!
       responses:
         '202':
           description: Response
@@ -7396,7 +7397,7 @@ paths:
     put:
       summary: Upload an enterprise license
       description: |-
-        Uploads an enterprise license. This operation does not automatically activate the license.
+        Uploads a new enterprise license. In order to apply it right away, use the `apply` query parameter.
 
         > [!NOTE]
         > The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).
@@ -214641,9 +214642,9 @@ components:
         type: string
     license-apply:
       name: apply
-      description: Whether to apply changes from the license. Uploading a license
-        does not automatically apply changes. To make the changes effective, you can
-        specify to apply the license too.
+      description: Whether to instantly apply changes from the license. Otherwise
+        the new license can be applied using the [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)
+        endpoint.
       in: query
       required: false
       schema:
diff --git a/descriptions-next/ghes-3.13/ghes-3.13.json b/descriptions-next/ghes-3.13/ghes-3.13.json
index 156dbbdca..31548169f 100644
--- a/descriptions-next/ghes-3.13/ghes-3.13.json
+++ b/descriptions-next/ghes-3.13/ghes-3.13.json
@@ -10429,15 +10429,15 @@
     },
     "/manage/v1/config/init": {
       "post": {
-        "summary": "Initialize instance configuration with license upload",
-        "description": "When you boot a GitHub instance for the first time, you can use this endpoint to upload a license.\n\nNote that you afterwards need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) to start the actual configuration process.\n\nThis endpoint also sets the root site administrator password which is used to authenticate with the GHES Manage API and the Management Console.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
+        "summary": "Initialize instance configuration with license and password",
+        "description": "When you boot and set up a GitHub instance for the first time, you can use this endpoint to upload a license and set the initial root site administrator password.\n\n> [!IMPORTANT]\n> To start the configuration process and apply the license, you need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)\n\nThe root site administrator password provided when calling this endpoint is used to authenticate for all other endpoints in the GHES Manage API and the Management Console UI.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
         "operationId": "enterprise-admin/initialize-instance-configuration",
         "tags": [
           "enterprise-admin"
         ],
         "externalDocs": {
           "description": "API method documentation",
-          "url": "https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-upload"
+          "url": "https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-and-password"
         },
         "servers": [
           {
@@ -10465,7 +10465,7 @@
                 "default": {
                   "value": {
                     "license": "@enterprise.ghl",
-                    "password": "secret-password!"
+                    "password": "provide-password-here!"
                   }
                 }
               }
@@ -10553,7 +10553,7 @@
       },
       "put": {
         "summary": "Upload an enterprise license",
-        "description": "Uploads an enterprise license. This operation does not automatically activate the license.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
+        "description": "Uploads a new enterprise license. In order to apply it right away, use the `apply` query parameter.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
         "operationId": "enterprise-admin/license-upload",
         "tags": [
           "enterprise-admin"
@@ -288402,7 +288402,7 @@
       },
       "license-apply": {
         "name": "apply",
-        "description": "Whether to apply changes from the license. Uploading a license does not automatically apply changes. To make the changes effective, you can specify to apply the license too.",
+        "description": "Whether to instantly apply changes from the license. Otherwise the new license can be applied using the [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) endpoint.",
         "in": "query",
         "required": false,
         "schema": {
diff --git a/descriptions-next/ghes-3.13/ghes-3.13.yaml b/descriptions-next/ghes-3.13/ghes-3.13.yaml
index 86d96ad28..5214390b1 100644
--- a/descriptions-next/ghes-3.13/ghes-3.13.yaml
+++ b/descriptions-next/ghes-3.13/ghes-3.13.yaml
@@ -7304,13 +7304,14 @@ paths:
         subcategory: manage-ghes
   "/manage/v1/config/init":
     post:
-      summary: Initialize instance configuration with license upload
+      summary: Initialize instance configuration with license and password
       description: |-
-        When you boot a GitHub instance for the first time, you can use this endpoint to upload a license.
+        When you boot and set up a GitHub instance for the first time, you can use this endpoint to upload a license and set the initial root site administrator password.
 
-        Note that you afterwards need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) to start the actual configuration process.
+        > [!IMPORTANT]
+        > To start the configuration process and apply the license, you need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)
 
-        This endpoint also sets the root site administrator password which is used to authenticate with the GHES Manage API and the Management Console.
+        The root site administrator password provided when calling this endpoint is used to authenticate for all other endpoints in the GHES Manage API and the Management Console UI.
 
         > [!NOTE]
         > The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).
@@ -7319,7 +7320,7 @@ paths:
       - enterprise-admin
       externalDocs:
         description: API method documentation
-        url: https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-upload
+        url: https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-and-password
       servers:
       - url: "{protocol}://{hostname}"
         variables:
@@ -7339,7 +7340,7 @@ paths:
               default:
                 value:
                   license: "@enterprise.ghl"
-                  password: secret-password!
+                  password: provide-password-here!
       responses:
         '202':
           description: Response
@@ -7396,7 +7397,7 @@ paths:
     put:
       summary: Upload an enterprise license
       description: |-
-        Uploads an enterprise license. This operation does not automatically activate the license.
+        Uploads a new enterprise license. In order to apply it right away, use the `apply` query parameter.
 
         > [!NOTE]
         > The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).
@@ -214641,9 +214642,9 @@ components:
         type: string
     license-apply:
       name: apply
-      description: Whether to apply changes from the license. Uploading a license
-        does not automatically apply changes. To make the changes effective, you can
-        specify to apply the license too.
+      description: Whether to instantly apply changes from the license. Otherwise
+        the new license can be applied using the [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.13/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)
+        endpoint.
       in: query
       required: false
       schema:
diff --git a/descriptions-next/ghes-3.14/dereferenced/ghes-3.14.2022-11-28.deref.json b/descriptions-next/ghes-3.14/dereferenced/ghes-3.14.2022-11-28.deref.json
index 6a8343deb..d9cded6e7 100644
--- a/descriptions-next/ghes-3.14/dereferenced/ghes-3.14.2022-11-28.deref.json
+++ b/descriptions-next/ghes-3.14/dereferenced/ghes-3.14.2022-11-28.deref.json
@@ -68642,15 +68642,15 @@
     },
     "/manage/v1/config/init": {
       "post": {
-        "summary": "Initialize instance configuration with license upload",
-        "description": "When you boot a GitHub instance for the first time, you can use this endpoint to upload a license.\n\nNote that you afterwards need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.14/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) to start the actual configuration process.\n\nThis endpoint also sets the root site administrator password which is used to authenticate with the GHES Manage API and the Management Console.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
+        "summary": "Initialize instance configuration with license and password",
+        "description": "When you boot and set up a GitHub instance for the first time, you can use this endpoint to upload a license and set the initial root site administrator password.\n\n> [!IMPORTANT]\n> To start the configuration process and apply the license, you need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/enterprise-server@3.14/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)\n\nThe root site administrator password provided when calling this endpoint is used to authenticate for all other endpoints in the GHES Manage API and the Management Console UI.\n\n> [!NOTE]\n> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F).",
         "operationId": "enterprise-admin/initialize-instance-configuration",
         "tags": [
           "enterprise-admin"
         ],
         "externalDocs": {
           "description": "API method documentation",
-          "url": "https://docs.github.com/enterprise-server@3.14/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-upload"
+          "url": "https://docs.github.com/enterprise-server@3.14/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-and-password"
         },
         "servers": [
           {
@@ -68693,7 +68693,7 @@
                 "default": {
                   "value": {
                     "license": "@enterprise.ghl",
-                    "password": "secret-password!"
+                    "password": "provide-password-here!"
                   }
                 }
               }
@@ -68888,7 +68888,7 @@
       },
       "put": {
         "summary": "Upload an enterprise license",
-        "description": "Uploads an enterprise license. Thi{"code":"internal","msg":"git-diff-tree: context deadline exceeded","meta":{"cause":"*fmt.wrapError"}}