[EDI] Detaching repositories from their security configurations (#59991)

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Author: isaacmbrown

content/code-security/how-tos/secure-at-scale/configure-organization-security/manage-your-coverage/detaching-repositories-from-their-security-configurations.md

@@ -1,7 +1,7 @@
 ---
 title: Detaching repositories from their security configurations
 shortTitle: Detach security configuration
-intro: You can unlink repositories from their {% data variables.product.prodname_security_configurations %} and instead manage their security enablement settings at the repository level.
+intro: Go back to managing a repository's security settings on an individual basis.
 permissions: '{% data reusables.permissions.security-org-enable %}'
 versions:
   feature: security-configurations
@@ -15,9 +15,9 @@ redirect_from:
 contentType: how-tos
 ---
 
-## About detaching repositories from their {% data variables.product.prodname_security_configurations %}
+If you decide that the security needs of a repository are too specific for a {% data variables.product.prodname_security_configuration %} to be useful, you can detach that repository from the linked configuration and instead manage security enablement settings at the repository level.
 
-If you decide that the security needs of a repository are too specific for a {% data variables.product.prodname_security_configuration %} to be useful, you can detach that repository from the linked configuration and instead manage security enablement settings at the repository level. Detaching a repository from a {% data variables.product.prodname_security_configuration %} will not change the existing security enablement settings for that repository. For an introduction to securing your repository at the repository level, see [AUTOTITLE](/code-security/getting-started/securing-your-repository).
+Detaching a repository from a {% data variables.product.prodname_security_configuration %} will not change the existing security enablement settings for that repository.
 
 Alternatively, if you want to apply a {% data variables.product.prodname_security_configuration %} to a repository that's already attached to a different configuration, you can apply the configuration as normal, and you do not need to detach the current configuration. For more information, see {% ifversion security-configurations-cloud %}[AUTOTITLE](/code-security/securing-your-organization/enabling-security-features-in-your-organization/applying-the-github-recommended-security-configuration-in-your-organization) and {% endif %}[AUTOTITLE](/code-security/securing-your-organization/enabling-security-features-in-your-organization/applying-a-custom-security-configuration).
 
@@ -30,3 +30,7 @@ Alternatively, if you want to apply a {% data variables.product.prodname_securit
 {% data reusables.security-configurations.select-repos %}
 1. Select the **Apply configuration** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **No configuration**.
 1. To finish detaching your repositories from their linked {% data variables.product.prodname_security_configurations %}, in the "No configuration?" window, click **No configuration**.
+
+## Next steps
+
+You can now manage security enablement settings at the repository level. For an introduction, see [AUTOTITLE](/code-security/getting-started/securing-your-repository).