Enterprise bug fix hour for week of December 4, 2023 (#47504)

Co-authored-by: Vanessa <vgrl@github.com>

content/admin/backing-up-and-restoring-your-instance/configuring-backups-on-your-instance.md

@@ -174,6 +174,7 @@ Network settings are excluded from the backup snapshot. After restoration, you m
 
 1. Ensure maintenance mode is enabled on the primary instance and all active processes have completed. For more information, see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)."
 1. Stop replication on all replica nodes in a high-availability configuration. For more information, see "[AUTOTITLE](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration#ghe-repl-stop)."
+1. Provision a new {% data variables.product.product_name %} instance to use as a target for the restoration of your backup. For more information, see "[AUTOTITLE](/admin/installation/setting-up-a-github-enterprise-server-instance)."
 1. If {% data variables.location.product_location %} has {% data variables.product.prodname_actions %} enabled, you must configure the external storage provider for {% data variables.product.prodname_actions %} on the replacement instance. For more information, see "[AUTOTITLE](/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)."
 
 ### Starting the restore operation

content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md

@@ -114,6 +114,8 @@ When this option is selected, the certificate is validated to make sure:
 
 You can establish role-based access control for users from your LDAP server by synchronizing {% data variables.product.prodname_ghe_server %} users and team membership against your established LDAP groups. For more information, see "[AUTOTITLE](/organizations/organizing-members-into-teams/creating-a-team#creating-teams-with-ldap-sync-enabled)."
 
+LDAP sync does not create user accounts on {% data variables.location.product_location %}. For more information, see "[Viewing and creating LDAP users](#viewing-and-creating-ldap-users)."
+
 {% note %}
 
 **Note:** Using LDAP Synchronization with groups that exceed 1499 members may lead to team membership synchronization failures.
@@ -124,7 +126,7 @@ If you need help determining if modifying the `MaxValRange` is the right approac
 
 {% endnote %}
 
-To enable LDAP Sync, in your LDAP settings, select **Synchronize Emails**, **Synchronize SSH Keys**, or **Synchronize GPG Keys** .
+To enable LDAP Sync, in your LDAP settings, select **Synchronize Emails**, **Synchronize SSH Keys**, or **Synchronize GPG Keys**.
 
 After you enable LDAP sync, a synchronization job will run at the specified time interval to perform the following operations on each user account:
 
@@ -188,6 +190,8 @@ If disclosing such information is not desired, your company or organization shou
 
 ## Viewing and creating LDAP users
 
+When you use LDAP, your instance creates a user account the first time someone successfully signs in using LDAP credentials. Alternatively, you can manually provision a user account.
+
 You can view the full list of LDAP users who have access to your instance and provision new users.
 
 {% data reusables.enterprise_site_admin_settings.sign-in %}

content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/managing-dormant-users.md

@@ -8,6 +8,7 @@ redirect_from:
   - /admin/user-management/managing-dormant-users
   - /admin/user-management/managing-users-in-your-enterprise/managing-dormant-users
 intro: '{% data reusables.enterprise-accounts.dormant-user-activity-threshold %}'
+permissions: "{% ifversion ghec or ghae %}Enterprise owners can manage dormant users for an enterprise.{% elsif ghes %}Site administrators can manage dormant users on a {% data variables.product.product_name %} instance.{% endif %}"
 versions:
   ghec: '*'
   ghes: '*'
@@ -37,12 +38,14 @@ You can customize the dormancy threshold for {% data variables.location.product_
 
 Dormancy applies to both enterprise members and outside collaborators.
 
+{% ifversion ghes %}
+
 ## Viewing dormant users
 
 {% data reusables.enterprise-accounts.viewing-dormant-users %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-1. In the left sidebar, click **Dormant users**.{% ifversion ghes %}
+1. In the left sidebar, click **Dormant users**.
 1. To suspend all the dormant users in this list, at the top of the page, click **Suspend all**.
 
 ## Determining whether a user account is dormant
@@ -62,6 +65,7 @@ Dormancy applies to both enterprise members and outside collaborators.
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.options-tab %}
 1. Under "Dormancy threshold", select the dropdown menu, and click the desired dormancy threshold.
+
 {% endif %}
 
 {% ifversion ghec %}

content/billing/managing-the-plan-for-your-github-account/about-per-user-pricing.md

@@ -108,11 +108,11 @@ If your enterprise does not use {% data variables.product.prodname_emus %}, you
 
 ### Accounts that consume a license on {% data variables.product.prodname_ghe_server %}
 
-Each user account on {% data variables.product.prodname_ghe_server %} consumes a seat.
+After a user successfully authenticates to a {% data variables.product.prodname_ghe_server %} instance for the first time, the user consumes a seat.
 
 Suspended users are not counted when calculating the number of licensed users consuming seats. For more information, see "[Suspending and unsuspending users]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %}
 
-Dormant users do occupy a seat license. As such, you can choose to suspend dormant users to release user licenses. For more information, see "[Managing dormant users]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %}
+Dormant users do occupy a seat license. Administrators can suspend dormant users to free licenses. For more information, see "[Managing dormant users]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %}
 
 {% endif %}
 

content/contributing/style-guide-and-content-model/style-guide.md

@@ -217,6 +217,14 @@ Use italics to emphasize words or parts of a sentence. Use emphasis sparingly fo
 - **Use:** _For types of packages other than containers_, to the right of the package version click **Delete**.
 - **Avoid:** Next to _**Title**_, add a descriptive label for your new key.
 
+## Error messages
+
+When you include the text of an error message from a {% data variables.product.company_short %} product or interface in an article, format the text according to the interface where the message appears.
+
+- If the message appears in {% data variables.product.prodname_dotcom %}'s web interface, or in a graphical client app like {% data variables.product.prodname_desktop %} or {% data variables.product.prodname_mobile %}, treat the message like other text in the UI. For more information, see "[User interface text](#user-interface-text)."
+
+- If the message appears in a command-line interface, log output, or a response from an API, reproduce the text exactly and use backticks to format the message using a monospaced font.
+
 ## Footnotes
 
 Avoid using footnotes where possible. Consider instead whether you could use a [callout](#callouts) or present the information in another way. See some [examples of alternatives to footnotes from NICE.org.uk](https://www.nice.org.uk/corporate/ecd6/chapter/footnotes).
@@ -841,6 +849,7 @@ A release note for a bug fix answers the following questions.
 - Language like "fixed a bug..." or "fixed an issue..." is implied and unnecessary.
 - To reduce repetition and unnecessary words, "now" is usually implied.
 - To clarify actors and impact, avoid passive language when possible.
+- If the release note includes an error message, format the message according to the guidance in "[Error messages](#error-messages)."
 
 #### Examples of release notes for bug fixes
 
@@ -896,6 +905,7 @@ A release note for a known issue answers the following questions.
 
 - To clarify actors and impact, avoid passive language when possible.
 - To reduce repetition and unnecessary words, "now" is usually implied.
+- If the release note includes an error message, format the message according to the guidance in "[Error messages](#error-messages)."
 - If useful, include relevant links to GitHub Docs.
 - Known issues are also a type of content on GitHub Docs. For more information, see "[AUTOTITLE](/contributing/style-guide-and-content-model/troubleshooting-content-type#known-issues)." If useful, write or link to more in-depth and contextually relevant content in the docs.