(DOCSP-39619) Updates upgrade details per help case. (#219)

- [DOCSP-39619](https://jira.mongodb.org/browse/DOCSP-39619)
- STAGING:
- [Upgrade OM: Step
4](https://preview-mongodberabilmdb.gatsbyjs.io/ops-manager/DOCSP-39619/tutorial/upgrade-ops-manager/#replace-init-files-with-symlinks)
- [Upgrade OM: Note in Step
5](https://preview-mongodberabilmdb.gatsbyjs.io/ops-manager/DOCSP-39619/tutorial/upgrade-ops-manager/#start-on-the-upgraded-host-1)

- [LATEST BUILD
LOG](https://workerpool-boxgs.mongodbstitch.com/pages/job.html?collName=queue&jobId=6650d2c7cf5bec1c29602080)

### Self-Review Checklist

- [ ]
[Define](https://wiki.corp.mongodb.com/display/DE/Taxonomy+tagging+instructions)
taxonomy
[values](https://wiki.corp.mongodb.com/display/DE/Docs+Taxonomy) at top
of page.
- [ ] Add genre facets (tutorial or reference), as in this [example
PR](10gen/cloud-docs#5042).
- [ ] Add programmingLanguage (if necessary).
- [ ] Add meta keywords (if necessary).
- [ ] Resolve any new warnings or errors in the build.
- [ ] Proofread for spelling and grammatical errors.
- [ ] Check staging for rendering issues.
- [ ] Confirm links are working.

Author: erabil-mdb

source/includes/fact-upgrade-logs-paused.rst

@@ -0,0 +1,5 @@
+.. note::
+
+   The logs that |onprem| generates during startup may temporarily pause 
+   at ``Starting pre-flight checks`` while |onprem| upgrades all its servers
+   to the same version.

source/includes/steps-upgrade-on-prem-with-deb-packages.yaml

@@ -71,10 +71,7 @@ level: 4
 title: "*[Optional]* Repeat the preceding steps for all other |onprem| hosts in your High Availability deployment."
 ref: rinse-repeat
 content: |
-  .. note::
-
-     The logs that generate from starting |onprem| service can be expected to temporarily pause 
-     logging at ``Starting pre-flight checks`` until all |onprem| servers upgrade to the same version.
+  .. include:: /includes/fact-upgrade-logs-paused.rst
   
   If your upgrade is successful, repeat steps 1 to 4 on the next host in your
   high availability |onprem| deployment.

source/includes/steps-upgrade-on-prem-with-rpm-packages.yaml

@@ -77,12 +77,25 @@ content: |
 
   a. Issue the following commands to move the old ``init`` files:
 
-     .. code-block:: sh
+     .. tabs::
+
+        .. tab:: Upgrading to 6.0
+           :tabid: upgrade-6
+
+           .. code-block:: sh
+
+              sudo mv /etc/init.d/mongodb-mms /etc/init.d/mongodb-mms-5.0
+              sudo mv /etc/init.d/mongodb-mms-backup-daemon /etc/init.d/        mongodb-mms-backup-daemon-5.0
+
+        .. tab:: Upgrading to 7.0
+           :tabid: upgrade-7
+     
+           .. code-block:: sh
 
-        sudo mv /etc/init.d/mongodb-mms /etc/init.d/mongodb-mms-4.0
-        sudo mv /etc/init.d/mongodb-mms-backup-daemon /etc/init.d/mongodb-mms-backup-daemon-4.0
+              sudo mv /etc/init.d/mongodb-mms /etc/init.d/mongodb-mms-6.0
+              sudo mv /etc/init.d/mongodb-mms-backup-daemon /etc/init.d/        mongodb-mms-backup-daemon-6.0
 
-  #. Issue the following commands to symbollically link the |onprem|
+  #. Issue the following commands to symbolically link the |onprem|
      files to their ``init`` files:
 
      .. code-block:: sh
@@ -111,7 +124,7 @@ content: |
      
      sudo /etc/init.d/mongodb-mms start
 
-  .. include:: /includes/note-backup-daemon-will-wait.rst
+  .. include:: /includes/fact-upgrade-logs-paused.rst
 
 ---
 stepnum: 6