diff --git a/content/admin/overview/best-practices-for-enterprises.md b/content/admin/overview/best-practices-for-enterprises.md
index 5ad36aa80c83..a3d9f9dfca05 100644
--- a/content/admin/overview/best-practices-for-enterprises.md
+++ b/content/admin/overview/best-practices-for-enterprises.md
@@ -56,6 +56,10 @@ You can manage the display of usernames within your enterprise's private reposit
 
 {% endif %}
 
+## Maintain ownership continuity
+
+Organizations can have more than one organization owner to avoid lapses in ownership. We recommend that at least two people within each organization have the owner role. For more information, see [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization).
+
 ## Further reading
 
 * [AUTOTITLE](/repositories/creating-and-managing-repositories/best-practices-for-repositories)
diff --git a/content/contributing/style-guide-and-content-model/style-guide.md b/content/contributing/style-guide-and-content-model/style-guide.md
index bdd735ade28f..c4ed539664da 100644
--- a/content/contributing/style-guide-and-content-model/style-guide.md
+++ b/content/contributing/style-guide-and-content-model/style-guide.md
@@ -1561,7 +1561,8 @@ We only document the responsive states of UI elements when they create ambiguity
 
 ### User interface text
 
-When referencing text in the user interface, reproduce the text exactly. Use quotation marks to surround UI text that cannot be interacted with.
+When referencing text in the user interface, reproduce the text exactly. Use quotation marks to surround UI text that cannot be interacted with. Place any commas outside of the quotation marks.
+
 * **Use:** Under “IP allow list”, click **Edit**.
 
 ### More resources
diff --git a/content/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products.md b/content/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products.md
index 6e2c0a22cf6d..bc60db557f83 100644
--- a/content/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products.md
+++ b/content/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products.md
@@ -103,6 +103,12 @@ Even if you change your organizational structure, you can still prepare a script
 
 {% data reusables.enterprise-migration-tool.organization-structure-tasks %}
 
+## What is our plan for the enterprise and organization names?
+
+If you are migrating between accounts on {% data variables.product.prodname_dotcom_the_website %}, keep in mind that there are naming constraints for user, organization, and enterprise accounts. If you need to re-use an organization or enterprise name for the migration, we recommend renaming accounts before as opposed to deleting them. Renaming makes a user, organization or enterprise account name available immediately for re-use.
+
+Organization accounts on {% data variables.product.prodname_enterprise %} share the same namespace; two user/organization accounts cannot have the same name. Enterprise accounts on {% data variables.product.prodname_enterprise %} share the same namespace; two enterprise accounts cannot have the same name.
+
 ## Running your migrations
 
 {% data reusables.enterprise-migration-tool.running-your-migrations %}