Skip to content

Commit a18ce0d

Browse files
Update content/admin/upgrading-your-instance/performing-an-upgrade/upgrading-with-an-upgrade-package.md
1 parent 3f5ad23 commit a18ce0d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/admin/upgrading-your-instance/performing-an-upgrade/upgrading-with-an-upgrade-package.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ While you can use a hotpatch to upgrade to the latest patch release within a fea
6767
6868
## Upgrading an instance with multiple nodes using an upgrade package
6969

70-
To upgrade a multi-node GitHub Enterprise Server environment using an upgrade package, you must first upgrade the primary node and wait for its configuration run to complete successfully. Only after the primary is fully upgraded and configured can you proceed to upgrade any replica or additional nodes. Attempting to upgrade other nodes before the primary is complete will result in upgrade failures.
70+
To upgrade a multi-node {% data variables.product.prodname_ghe_server %} environment using an upgrade package, you must first upgrade the primary node and wait for its configuration run to complete successfully. Only after the primary is fully upgraded and configured can you proceed to upgrade any replica or additional nodes. Attempting to upgrade other nodes before the primary is complete will result in upgrade failures.
7171

7272
* [Upgrading the primary node with an upgrade package](#upgrading-the-primary-node-with-an-upgrade-package)
7373
* [Upgrading additional nodes with an upgrade package](#upgrading-additional-nodes-with-an-upgrade-package)

0 commit comments

Comments
 (0)