From 8d02d4aa4c2f0697e8c1baa1c5b4eadd5ccf8d52 Mon Sep 17 00:00:00 2001 From: Alfredo Deza Date: Tue, 6 Mar 2018 16:11:03 -0500 Subject: [PATCH] doc/ceph-volume update stdin as monospaced Signed-off-by: Alfredo Deza --- doc/ceph-volume/lvm/activate.rst | 2 +- doc/ceph-volume/lvm/encryption.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/ceph-volume/lvm/activate.rst b/doc/ceph-volume/lvm/activate.rst index 9b7aa43fa45..3990a3d53f3 100644 --- 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 02a447b5779..07207f1aa99 100644 --- 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::