[pve-devel] applied: [PATCH docs] pveceph minor language corrections

Thomas Lamprecht t.lamprecht at proxmox.com
Mon Feb 18 09:02:33 CET 2019


Am 2/14/19 um 4:01 PM schrieb Oguz Bektas:
> Signed-off-by: Oguz Bektas <o.bektas at proxmox.com>
> ---
>  pveceph.adoc | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/pveceph.adoc b/pveceph.adoc
> index c90a92e..3af8431 100644
> --- a/pveceph.adoc
> +++ b/pveceph.adoc
> @@ -211,7 +211,7 @@ This is the default when creating OSDs in Ceph luminous.
>  pveceph createosd /dev/sd[X]
>  ----
>  
> -NOTE: In order to select a disk in the GUI, to be more failsafe, the disk needs
> +NOTE: In order to select a disk in the GUI, to be more fail-safe, the disk needs
>  to have a GPT footnoteref:[GPT, GPT partition table
>  https://en.wikipedia.org/wiki/GUID_Partition_Table] partition table. You can
>  create this with `gdisk /dev/sd(x)`. If there is no GPT, you cannot select the
> @@ -227,7 +227,7 @@ pveceph createosd /dev/sd[X] -journal_dev /dev/sd[Y]
>  ----
>  
>  NOTE: The DB stores BlueStore’s internal metadata and the WAL is BlueStore’s
> -internal journal or write-ahead log. It is recommended to use a fast SSDs or
> +internal journal or write-ahead log. It is recommended to use a fast SSD or
>  NVRAM for better performance.
>  
>  
> @@ -235,7 +235,7 @@ Ceph Filestore
>  ~~~~~~~~~~~~~
>  Till Ceph luminous, Filestore was used as storage type for Ceph OSDs. It can
>  still be used and might give better performance in small setups, when backed by
> -a NVMe SSD or similar.
> +an NVMe SSD or similar.
>  
>  [source,bash]
>  ----
> 

applied



More information about the pve-devel mailing list