Added '`' around values for readability

docs/parameters.yaml

@@ -162,23 +162,23 @@ description: |+
   Cms basically is a file (or asset) discovery service. Each server has a cmsd daemon which
   connect to a master one informing it if a server is available. XRootD asks cms where a file
   could be found and cms works to report back the server for where the file is located.
-  Accepted values: trace, debug, info, warn, error, fatal, panic
+  Accepted values: `trace`, `debug`, `info`, `warn`, `error`, `fatal`, `panic`
 type: string
 default: error
 components: ["origin"]
 ---
 name: Logging.Origin.Scitokens
 description: |+
   Trace level of scitokens debug output within XRootD configuration. This entails token management
-  and security credentials within XRootD. Accepted values: trace, debug, info, warn, error, fatal, panic
+  and security credentials within XRootD. Accepted values: `trace`, `debug`, `info`, `warn`, `error`, `fatal`, `panic`
 type: string
 default: error
 components: ["origin"]
 ---
 name: Logging.Origin.Xrd
 description: |+
   Trace level of the eXtended Request Daemon within XRootD, another main XRootD executable. This reports information
-  the XRootD protocol and works with cms. Accepted values: trace, debug, info, warn, error, fatal, panic
+  the XRootD protocol and works with cms. Accepted values: `trace`, `debug`, `info`, `warn`, `error`, `fatal`, `panic`
 type: string
 default: error
 components: ["origin"]
@@ -187,15 +187,15 @@ name: Logging.Origin.Xrootd
 description: |+
   Trace options for XRootD debug output within XRootD configuration. This prefix is reserved for the xroot protocol,
   which is the component that sits on sockets and talks to clients as they query file-system info, open files, and read data.
-  This is the protocol for XRootD (like http) and handles connections and requests. Accepted values: trace, debug, info, warn, error, fatal, panic
+  This is the protocol for XRootD (like http) and handles connections and requests. Accepted values: `trace`, `debug`, `info`, `warn`, `error`, `fatal`, `panic`
 type: string
 default: info
 components: ["origin"]
 ---
 name: Logging.Origin.Http
 description: >-
   Logging level for the HTTP component of the origin. Increasing to debug will cause the Xrootd daemon to log.
-  Accepted values: trace, debug, info, warn, error, fatal, panic
+  Accepted values: `trace`, `debug`, `info`, `warn`, `error`, `fatal`, `panic`
   all headers and requests.
 type: string
 default: error
@@ -204,23 +204,23 @@ components: ["origin"]
 name: Logging.Origin.Ofs
 description: >-
   Logging level of Xrootd's "Open File System" (ofs) subsystem.  The OFS manages the file descriptor table and redirection/
-  error handling. Accepted values: trace, debug, info, warn, error, fatal, panic
+  error handling. Accepted values: `trace`, `debug`, `info`, `warn`, `error`, `fatal`, `panic`
 type: string
 default: error
 components: ["origin"]
 ---
 name: Logging.Origin.Oss
 description: >-
   Logging level of Xrootd's "Open Storage System" (oss) subsystem.  The OSS manages the interaction with the underlying
-  POSIX storage (open, read, write, close, etc). Accepted values: trace, debug, info, warn, error, fatal, panic
+  POSIX storage (open, read, write, close, etc). Accepted values: `trace`, `debug`, `info`, `warn`, `error`, `fatal`, `panic`
 type: string
 default: error
 components: ["origin"]
 ---
 name: Logging.Cache.Http
 description: >-
   Logging level for the HTTP component of the cache.  Increasing to debug will cause the Xrootd daemon to log
-  all headers and requests. Accepted values: trace, debug, info, warn, error, fatal, panic
+  all headers and requests. Accepted values: `trace`, `debug`, `info`, `warn`, `error`, `fatal`, `panic`
 type: string
 default: error
 components: ["cache"]
@@ -229,7 +229,7 @@ name: Logging.Cache.Ofs
 description: |+
   Trace level of XRootD's Open File System. This component cares about files and directories from the administrative perspective.
   This component is build on top of the Open Storage System component, which deals with things like file creation and reads and
-  writes for files and directories. Accepted values: trace, debug, info, warn, error, fatal, panic
+  writes for files and directories. Accepted values: `trace`, `debug`, `info`, `warn`, `error`, `fatal`, `panic`
 type: string
 default: error
 components: ["cache"]
@@ -238,31 +238,31 @@ name: Logging.Cache.Pfc
 description: |+
   Trace level of XRootD Proxy File Cache (XCache), the caching mechanism used by XRootD. This component
   entails information for caches/caching within XRootD. This component instantiates its own Open Storage
-  System (OSS) to write local files to. Accepted values: trace, debug, info, warn, error, fatal, panic
+  System (OSS) to write local files to. Accepted values: `trace`, `debug`, `info`, `warn`, `error`, `fatal`, `panic`
 type: string
 default: info
 components: ["cache"]
 ---
 name: Logging.Cache.Pss
 description: |+
   Trace level of XRootD Proxy System Service. Variables this component reports include: number of remotes file opens,
-  number of opens that failed, number of remote file closes, and number of closes that failed. Accepted values: trace, debug, info, warn, error, fatal, panic
+  number of opens that failed, number of remote file closes, and number of closes that failed. Accepted values: `trace`, `debug`, `info`, `warn`, `error`, `fatal`, `panic`
 type: string
 default: error
 components: ["cache"]
 ---
 name: Logging.Cache.Scitokens
 description: |+
   Trace level of scitokens debug output within XRootD configuration. This entails token management
-  and security credentials within XRootD. Accepted values: trace, debug, info, warn, error, fatal, panic
+  and security credentials within XRootD. Accepted values: `trace`, `debug`, `info`, `warn`, `error`, `fatal`, `panic`
 type: string
 default: error
 components: ["cache"]
 ---
 name: Logging.Cache.Xrd
 description: |+
   Trace level of the eXtended Request Daemon within XRootD, another main XRootD executable. This reports information
-  the XRootD protocol and works with cms. Accepted values: trace, debug, info, warn, error, fatal, panic
+  the XRootD protocol and works with cms. Accepted values: `trace`, `debug`, `info`, `warn`, `error`, `fatal`, `panic`
 type: string
 default: error
 components: ["cache"]
@@ -271,7 +271,7 @@ name: Logging.Cache.Xrootd
 description: |+
   Trace options for XRootD debug output within XRootD configuration. This prefix is reserved for the xroot protocol,
   which is the component that sits on sockets and talks to clients as they query file-system info, open files, and read data.
-  This is the protocol for XRootD (like http) and handles connections and requests. Accepted values: trace, debug, info, warn, error, fatal, panic
+  This is the protocol for XRootD (like http) and handles connections and requests. Accepted values: `trace`, `debug`, `info`, `warn`, `error`, `fatal`, `panic`
 type: string
 default: error
 components: ["cache"]