From 817edfd1c70575d1a4582ac7da6f5b939c3e6b19 Mon Sep 17 00:00:00 2001 From: Prasanna Kumar Kalever Date: Wed, 11 Nov 2020 12:57:40 +0530 Subject: [PATCH] cleanup: remove the use of text in markdown We do not have `text` in the new section of the MarkDown Rules. Hence dropping them. Signed-off-by: Prasanna Kumar Kalever --- docs/capabilities.md | 8 ++++---- docs/development-guide.md | 6 +++--- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/capabilities.md b/docs/capabilities.md index cd2662c42..a4db72701 100644 --- a/docs/capabilities.md +++ b/docs/capabilities.md @@ -14,7 +14,7 @@ We have provisioner, controller expand and node stage secrets in storage class. For the provisioner and controller expand stage secret in storageclass, the user needs to have the below mentioned ceph capabilities. -```text +``` "mon", "profile rbd", "mgr", "allow rw", "osd", "profile rbd" @@ -23,7 +23,7 @@ user needs to have the below mentioned ceph capabilities. And for the node stage secret in storageclass, the user needs to have the below mentioned ceph capabilities. -```text +``` "mon", "profile rbd", "osd", "profile rbd", "mgr", "allow rw" @@ -34,7 +34,7 @@ below mentioned ceph capabilities. Similarly in CephFS, for the provisioner and controller expand stage secret in storageclass, the user needs to have the below mentioned ceph capabilities. -```text +``` "mon", "allow r", "mgr", "allow rw", "osd", "allow rw tag cephfs metadata=*" @@ -43,7 +43,7 @@ storageclass, the user needs to have the below mentioned ceph capabilities. And for node stage secret in storageclass, the user needs to have the below mentioned ceph capabilities. -```text +``` "mon", "allow r", "mgr", "allow rw", "osd", "allow rw tag cephfs *=*", diff --git a/docs/development-guide.md b/docs/development-guide.md index d75b035fa..05e2a34f1 100644 --- a/docs/development-guide.md +++ b/docs/development-guide.md @@ -119,7 +119,7 @@ contribution. See the [DCO](DCO) file for details. Contributors sign-off that they adhere to these requirements by adding a Signed-off-by line to commit messages. For example: -```text +``` subsystem: This is my commit message More details on what this commit does @@ -144,7 +144,7 @@ We follow a rough convention for commit messages that is designed to answer two questions: what changed and why? The subject line should feature the what and the body of the commit should describe the why. -```text +``` cephfs: update cephfs resize use cephfs resize to resize subvolume @@ -154,7 +154,7 @@ Signed-off-by: Random J Developer The format can be described more formally as follows: -```text +``` :