Update log-support.md

fixed the formatting issue for NONE and INFO

Author: sreejithgs

docs/log-support.md

@@ -9,7 +9,7 @@ The following logging severity levels are supported and the default value is `IN
 -  `ERROR`:  Only fatal messages and error messages are logged.
 -  `INFO`:  Only fatal, error, and informational messages are logged.
 
-For Kubernetes YAML based deployments the default value is NONE. But, for Helm and OpenShift operator deployments of NetScaler Observability Exporter logging is enabled by default and set as INFO.
+For Kubernetes YAML based deployments the default value is `NONE`. But, for Helm and OpenShift operator deployments of NetScaler Observability Exporter logging is enabled by default and set as `INFO`.
 
 You can configure logging using the environment variable `NSOE_LOG_LEVEL` while deploying NetScaler Observability Exporter for each endpoint.
 
@@ -24,4 +24,4 @@ The following are the types of logs that you can get:
 -  NetScaler Observability Exporter configuration file errors and parsing errors.
 -  Endpoint (ElasticSearch, Splunk) status such as up or down.
 -  Endpoint specific configuration errors. For example, the message saying `Kafka topic is invalid`.
--  NetScaler related configuration messages. For example, adding or deleting a NetScaler IP address.
+-  NetScaler related configuration messages. For example, adding or deleting a NetScaler IP address.