Repo sync

content/admin/managing-iam/configuring-authentication-for-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users.md

@@ -19,6 +19,10 @@ topics:
   - SSO
 ---
 
+**Before** following the steps in this article, make sure that your enterprise uses **managed users**. You can do so by checking whether your enterprise view has the "Users managed by ACCOUNT NAME" header bar at the top of the screen. If you see this, your enterprise uses **managed users** and you can follow the steps in this article.
+
+If your enterprise uses **personal accounts**, you must follow a different process to configure SAML single sign-on. See "[AUTOTITLE](/admin/managing-iam/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise)."
+
 ## About SAML SSO for {% data variables.product.prodname_emus %}
 
 With {% data variables.product.prodname_emus %}, access to your enterprise's resources on {% data variables.location.product_location %} must be authenticated through your identity provider (IdP). Instead of signing in to {% data variables.product.prodname_dotcom %} with a {% data variables.product.prodname_dotcom %} username and password, members of your enterprise will sign in through your IdP.

content/admin/managing-iam/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md

@@ -23,7 +23,13 @@ redirect_from:
   - /admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise
 ---
 
-{% data reusables.enterprise-accounts.emu-saml-note %}
+{% ifversion ghec %}
+
+**Before** following the steps in this article, make sure that your enterprise uses **personal accounts**. You can do so by checking whether your enterprise view has the "Users managed by ACCOUNT NAME" header bar at the top of the screen.
+
+If you see this, your enterprise uses **managed users** and you must follow a different process to configure SAML single sign-on. See "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users)."
+
+{% endif %}
 
 ## About SAML SSO
 

content/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/upgrading-a-cluster.md

@@ -37,7 +37,7 @@ Use an upgrade package to upgrade a {% data variables.product.prodname_ghe_serve
 
 ### Preparing to upgrade
 
-1. Review [Cluster network configuration](/admin/enterprise-management/configuring-clustering/cluster-network-configuration) for the version you are upgrading to, and update your configuration as needed.
+1. Review [AUTOTITLE](/admin/enterprise-management/configuring-clustering/cluster-network-configuration) for the version you are upgrading to, and update your configuration as needed.
 1. Back up your data with [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme).
 1. Schedule a maintenance window for end users of your {% data variables.product.prodname_ghe_server %} cluster, as it will be unavailable for normal use during the upgrade. Maintenance mode blocks user access and prevents data changes while the cluster upgrade is in progress.
 1. On the [{% data variables.product.prodname_ghe_server %} Download Page](https://enterprise.github.com/download), copy the URL for the upgrade _.pkg_ file to the clipboard.
@@ -75,7 +75,7 @@ Use an upgrade package to upgrade a {% data variables.product.prodname_ghe_serve
    1. On any `elasticsearch-server` node, run `/usr/local/share/enterprise/ghe-es-auditlog-cluster-rebalance`.
 {% endif %}
 1. **With the exception of the primary MySQL node**, connect to the administrative shell of each of the {% data variables.product.prodname_ghe_server %} nodes.
-Run the `ghe-upgrade` command, providing the package file name you downloaded in Step 4 of [Preparing to upgrade](#preparing-to-upgrade):
+Run the `ghe-upgrade` command, providing the package file name you downloaded in step 4 of [Preparing to upgrade](#preparing-to-upgrade):
 
    ```shell
    $ ghe-upgrade PACKAGE-FILENAME.pkg
@@ -89,7 +89,7 @@ Run the `ghe-upgrade` command, providing the package file name you downloaded in
    ```
 
 1. The upgrade process will reboot the node once it completes. Verify that you can `ping` each node after it reboots.
-1. Connect to the administrative shell of the primary MySQL node. Run the `ghe-upgrade` command, providing the package file name you downloaded in Step 4 of [Preparing to upgrade](#preparing-to-upgrade):
+1. Connect to the administrative shell of the primary MySQL node. Run the `ghe-upgrade` command, providing the package file name you downloaded in step 4 of [Preparing to upgrade](#preparing-to-upgrade):
 
    ```shell
    $ ghe-upgrade PACKAGE-FILENAME.pkg
@@ -102,7 +102,14 @@ Run the `ghe-upgrade` command, providing the package file name you downloaded in
    > gpg: Good signature from "GitHub Enterprise (Upgrade Package Key) > <[email protected]>"
    ```
 
-1. The upgrade process will reboot the primary MySQL node once it completes. Verify that you can `ping` each node after it reboots.{% ifversion ghes %}
+1. The upgrade process will reboot the primary MySQL node once it completes. Verify that you can `ping` each node after it reboots
+
+   > [!IMPORTANT] Before proceeding with the next step, you must wait for the post-upgrade configuration to complete. To monitor progress of the configuration run, read the output in `/data/user/common/ghe-config.log`. For example, you can tail the log by running the following command:
+   >
+   > ```shell
+   > tail -f /data/user/common/ghe-config.log
+   > ```
+
 1. Connect to the administrative shell of the primary MySQL node and run the `ghe-cluster-config-apply` command.
-1. When `ghe-cluster-config-apply` is complete, check that the services are in a healthy state by running `ghe-cluster-status`.{% endif %}
+1. When `ghe-cluster-config-apply` is complete, check that the services are in a healthy state by running `ghe-cluster-status`.
 1. Exit maintenance mode from the administrative shell of any node by running `ghe-cluster-maintenance -u`.

content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md

@@ -26,7 +26,7 @@ Members of your organization's Owners team can give _billing manager_ permission
 
 Billing managers can:
 
-* Upgrade or downgrade the account
+* Upgrade or downgrade between {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_team %} plans
 * Add, update, or remove payment methods
 * View payment history
 * Download receipts
@@ -37,6 +37,7 @@ In addition, all billing managers will receive billing receipts by email on the
 
 Billing managers **are not** able to:
 
+* Upgrade to {% data variables.product.prodname_enterprise %} or downgrade an enterprise account
 * Create or access repositories in your organizations
 * See private members of your organization
 * Be seen in the list of organization members

content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md

@@ -22,7 +22,7 @@ topics:
 
 {% data reusables.search.you-can-search-globally %}
 
-* To search globally across all of {% data variables.product.product_name %}, type what you're looking for into the search field at the top of any page, and choose "Search all of {% data variables.product.prodname_dotcom %}" in the search dropdown menu.
+* To search globally across all of {% data variables.product.product_name %}, type what you're looking for into the search field at the top of any page, and choose "Search all of {% data variables.product.prodname_dotcom %}"{% ifversion fpt or ghec or ghes < 3.12 %} in the search dropdown menu{% endif %}.
 * To search within a particular repository or organization, navigate to the repository or organization page, type what you're looking for into the search field at the top of the page, and press **Enter**.
 
   {% ifversion code-search-upgrade %}You can also use suggestions and completions in the search bar to quickly find what you need.