From: Sage Weil Date: Tue, 24 Oct 2017 12:30:05 +0000 (-0500) Subject: doc/release-notes: fix backticks X-Git-Tag: v13.0.1~421^2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=refs%2Fpull%2F18482%2Fhead;p=ceph.git doc/release-notes: fix backticks Signed-off-by: Sage Weil --- diff --git a/doc/release-notes.rst b/doc/release-notes.rst index 9eb756eda091..475a9b24b95f 100644 --- a/doc/release-notes.rst +++ b/doc/release-notes.rst @@ -724,8 +724,8 @@ upgrades from Jewel to Luminous. which means that a librados user might get fewer keys than they asked for. This is necessary to prevent careless users from requesting an unreasonable amount of data from the cluster in a single operation. The new limits are - configured with `osd_max_omap_entries_per_request`, defaulting to 131,072, and - 'osd_max_omap_bytes_per_request', defaulting to 4MB. + configured with ``osd_max_omap_entries_per_request``, defaulting to 131,072, and + ``osd_max_omap_bytes_per_request``, defaulting to 4MB. * Calculation of recovery priorities has been updated. This could lead to unintuitive recovery prioritization @@ -4264,8 +4264,8 @@ Upgrade notes which means that a librados user might get fewer keys than they asked for. This is necessary to prevent careless users from requesting an unreasonable amount of data from the cluster in a single operation. The new limits are - configured with `osd_max_omap_entries_per_request`, defaulting to 131,072, and - 'osd_max_omap_bytes_per_request', defaulting to 4MB. + configured with ``osd_max_omap_entries_per_request``, defaulting to 131,072, and + ``osd_max_omap_bytes_per_request``, defaulting to 4MB. * Calculation of recovery priorities has been updated. This could lead to unintuitive recovery prioritization