From: Sage Weil <sage@newdream.net>
Date: Thu, 25 Mar 2021 21:27:33 +0000 (-0500)
Subject: doc/releases/pacific: a few adjustments
X-Git-Tag: v17.1.0~2418^2~10
X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=1c2521e15c6a3b1de324904183cf765e1ddbf23f;p=ceph.git

doc/releases/pacific: a few adjustments

Signed-off-by: Sage Weil <sage@newdream.net>
---

diff --git a/doc/releases/pacific.rst b/doc/releases/pacific.rst
index d98736873be4..b3768e3385c6 100644
--- a/doc/releases/pacific.rst
+++ b/doc/releases/pacific.rst
@@ -214,6 +214,15 @@ Upgrading non-cephadm clusters
 
      # ceph osd unset noout
 
+#. Consider transitioning your cluster to use the cephadm deployment
+   and orchestration framework to simplify cluster management and
+   future upgrades.  For more information on converting an existing
+   cluster to cephadm, see :ref:`cephadm-adoption`.
+
+
+Post-upgrade
+~~~~~~~~~~~~
+
 #. Verify the cluster is healthy with ``ceph health``.
 
    If your CRUSH tunables are older than Hammer, Ceph will now issue a
@@ -238,8 +247,7 @@ Upgrading non-cephadm clusters
    Moving to 'straw2' buckets will unlock a few recent features, like
    the `crush-compat` :ref:`balancer <balancer>` mode added back in Luminous.
 
-
-#. If you did you already do so when upgrading from Mimic, we
+#. If you did not already do so when upgrading from Mimic, we
    recommened you enable the new :ref:`v2 network protocol <msgr2>`,
    issue the following command::
 
@@ -273,11 +281,6 @@ Upgrading non-cephadm clusters
    For more information about the telemetry module, see :ref:`the
    documentation <telemetry>`.
 
-#. Consider transitioning your cluster to use the cephadm deployment
-   and orchestration framework to simplify cluster management and
-   future upgrades.  For more information on converting an existing
-   cluster to cephadm, see :ref:`cephadm-adoption`.
-
 
 Upgrade from pre-Nautilus releases (like Mimic or Luminous)
 -----------------------------------------------------------