Repo sync

content/admin/backing-up-and-restoring-your-instance/restoring-from-a-backup.md

@@ -32,7 +32,7 @@ Before restoring a backup:
 
 1. **Enable maintenance mode** on the target instance. See [AUTOTITLE](/admin/administering-your-instance/configuring-maintenance-mode/enabling-and-scheduling-maintenance-mode).
 1. **Verify access** to the backup storage containing the snapshot.
-1. **Pause interfering services** — if using High Availability (HA), make sure replication is stopped.
+1. **Tear down replication**. If using High Availability (HA), run `ghe-repl-teardown` on the target instance. Stopping replication with `ghe-repl-stop` is not sufficient, because the target remains configured as part of a replication pair and the restore fails. See [AUTOTITLE](/admin/monitoring-and-managing-your-instance/configuring-high-availability/removing-a-high-availability-replica).
 1. **Prepare for {% data variables.product.prodname_actions %}** — if enabled, ensure the target instance is configured with the correct external storage. See [AUTOTITLE](/admin/backing-up-and-restoring-your-instance/restoring-with-github-actions-enabled) for details.
 
 ## Starting the restore operation

content/code-security/tutorials/trialing-github-advanced-security/trial-advanced-security.md

@@ -27,6 +27,7 @@ To set up a trial of {% data variables.product.prodname_GHAS %} using this metho
 1. You have not previously purchased {% data variables.product.prodname_GHAS %} (that is, you do not currently or in the past have a paid license for {% data variables.product.prodname_GHAS %}).
 1. You are not already using metered billing for {% data variables.product.prodname_GHAS %}.
 1. If you have had a previous {% data variables.product.prodname_GHAS %} trial, you are eligible only if you have had no more than one previous trial and it ended at least 180 days ago.
+1. Your enterprise has 300 or fewer seats.
 
 > [!TIP]
 > * **No enterprise account?** Start a trial of {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_GHAS %}. See [AUTOTITLE](/enterprise-cloud@latest/admin/overview/setting-up-a-trial-of-github-enterprise-cloud).

content/copilot/reference/enterprise-administrators/enterprise-managed-settings.md

@@ -161,7 +161,7 @@ Restricts plugin installation to only the marketplaces explicitly defined by the
 
 Sets your preferred model as the default for new conversations. This lets you choose the default model that best fits your enterprise's workflows. Users can still select a different model on a per-conversation basis.
 * Set `model` to `"auto"` to use {% data variables.copilot.copilot_auto_model_selection_short %} as the default, so new sessions choose a model automatically unless the user specifies a different model on a per-conversation basis. See [AUTOTITLE](/copilot/concepts/models/auto-model-selection).
-* Set `model` to a specific model and version to make that model the default for new conversations, for example `"kimi-k-3"`.
+* Set `model` to a specific model and version to make that model the default for new conversations, for example `"kimi-k3"`.
 
 This key is overridable by enterprise team mapping. In your `{% data variables.copilot.managed_setting_file %}`, use the `{ "overridable": "auto" }` syntax to specialize the key's configuration on a per-team basis. You can then set `"model": "unmanaged"` in a team settings file, providing a specialization that takes precedence over `{% data variables.copilot.managed_setting_file %}` for members of the subject team.
 

content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md

@@ -56,6 +56,8 @@ The content of public `README.md` will appear on your organization's public prof
 
 ## Adding a member-only organization profile README
 
+>[!NOTE] Member-only organization profile READMEs will only load from a `.github-private` repository with its visibility set to private. Repositories in enterprises set to internal visibility will not work.
+
 The content of a member-only `README.md` will be displayed in the member view of your organization's profile.
 
 1. If your organization does not already have a `.github-private` repository, create a private repository called `.github-private`.

data/release-notes/enterprise-server/3-22/0-rc1.yml

@@ -1,6 +1,6 @@
 date: '2026-08-11'
 release_candidate: true
-deprecated: false
+deprecated: true
 intro: |
   > [!NOTE] Release candidate (RC) builds are intended solely for use in a test environment. Do not install an RC in a production environment.
   >