doc/ceph-volume update stdin as monospaced

Signed-off-by: Alfredo Deza <adeza@redhat.com>

diff --git a/doc/ceph-volume/lvm/activate.rst b/doc/ceph-volume/lvm/activate.rst
index 9b7aa43fa45bcef820c1455e2905a9edd0dfea72..3990a3d53f3275c601d52d4508d51202cca29ed5 100644 (file)
--- a/doc/ceph-volume/lvm/activate.rst
+++ b/doc/ceph-volume/lvm/activate.rst
@@ -67,7 +67,7 @@ ensure that the correct device is linked.
 
 Existing OSDs
 -------------
-For exsiting OSDs that have been deployed with different tooling, the only way
+For existing OSDs that have been deployed with different tooling, the only way
 to port them over to the new mechanism is to prepare them again (losing data).
 See :ref:`ceph-volume-lvm-existing-osds` for details on how to proceed.
 

diff --git a/doc/ceph-volume/lvm/encryption.rst b/doc/ceph-volume/lvm/encryption.rst
index 02a447b5779210b9acb656762bb155bb29244404..07207f1aa99d0c8b272cfe1bafeee61c7695ce2f 100644 (file)
--- a/doc/ceph-volume/lvm/encryption.rst
+++ b/doc/ceph-volume/lvm/encryption.rst
@@ -38,7 +38,7 @@ volume setups, since encryption will happen once the LV is created.
 Workflow
 --------
 When setting up the OSD, a secret key will be created, that will be passed
-along to the monitor in JSON format as stdin to prevent the key from being
+along to the monitor in JSON format as ``stdin`` to prevent the key from being
 captured in the logs.
 
 The JSON payload looks something like::