Words and 💄

Author: lildude

README.md

@@ -3,11 +3,11 @@
 This repository includes backup and recovery utilities for [GitHub Enterprise][1].
 
 **Note**: the [GitHub Enterprise version requirements](docs/requirements.md#github-enterprise-version-requirements) have
-changed starting with Backup Utilities (backup-utils) v2.13.0.
+changed starting with Backup Utilities v2.13.0.
 
 ### Features
 
-The Backup Utilities implement a number of advanced capabilities for backup
+Backup Utilities implement a number of advanced capabilities for backup
 hosts, built on top of the backup and restore features already included in
 GitHub Enterprise.
 
@@ -48,16 +48,3 @@ site setup or recovery, please contact our [Enterprise support team][2] instead.
 
 [1]: https://enterprise.github.com
 [2]: https://enterprise.github.com/support/
-
-
-
-
-
-
-
-
-[6]: https://enterprise.github.com/help/articles/upgrading-to-a-newer-release
-[8]: https://enterprise.github.com/help/articles/backing-up-enterprise-data
-[9]: https://enterprise.github.com/help/articles/restoring-enterprise-data
-[10]: https://help.github.com/enterprise/2.0/admin-guide/migrating-to-a-different-platform-or-from-github-enterprise-11-10-34x/
-[11]: https://help.github.com/enterprise/2.0/admin-guide/

docs/faq.md

@@ -11,9 +11,9 @@ datastores. This active/passive cluster configuration is designed to minimize
 service disruption in the event of hardware failure or major network outage
 affecting the primary instance. Because some forms of data corruption or loss may
 be replicated immediately from primary to replica, it is not a replacement for
-the Backup Utilities as part of your disaster recovery plan.
+Backup Utilities as part of your disaster recovery plan.
 
-### The purpose of the Backup Utilities
+### The purpose of Backup Utilities
 Backup Utilities are a disaster recovery tool. This tool takes date-stamped
 snapshots of all major datastores. These snapshots are used to restore an instance
 to a prior state or set up a new instance without having another always-on GitHub

docs/requirements.md

@@ -1,6 +1,6 @@
 # Requirements
 
-The Backup Utilities should be run on a host dedicated to long-term permanent
+Backup Utilities should be run on a host dedicated to long-term permanent
 storage and must have network connectivity with the GitHub Enterprise appliance.
 
 ## Backup host requirements
@@ -21,7 +21,7 @@ patterns of the GitHub appliance. We recommend allocating at least 5x the amount
 of storage allocated to the primary GitHub appliance for historical snapshots
 and growth over time.
 
-The backup utilities use [hard links][5] to store data efficiently, and the
+Backup Utilities use [hard links][5] to store data efficiently, and the
 repositories on GitHub Enterprise use [symbolic links][6] so the backup snapshots
 must be written to a filesystem with support for symbolic and hard links.