minor updates

docs/basic_usage.md

@@ -1,4 +1,4 @@
-The following examples demonstrate the basic usage of the `gnmic` in a scenario where the remote target runs insecure (not TLS enabled) gNMI server. The `admin:admin` credentials are used to connect to the gNMI server running at `10.1.0.11:57400` address.
+The following examples demonstrate the basic usage of `gnmic` in a scenario where the remote target runs an unsecured (without TLS enabled) gNMI server. The `admin:admin` credentials are used to connect to the gNMI server running at `10.1.0.11:57400` address.
 
 !!!info
     For the complete command usage examples, refer to the ["Command reference"](cmd/capabilities.md) menu.

docs/cmd/capabilities.md

@@ -1,4 +1,5 @@
 ## Description
+
 The `[cap | capabilities]` command represents the [gNMI Capabilities RPC](https://github.com/openconfig/gnmi/blob/master/proto/gnmi/gnmi.proto#L51).
 
 It is used to send a [Capability Request](https://github.com/openconfig/gnmi/blob/master/proto/gnmi/gnmi.proto#L431) to the specified target(s) and expects one [Capability Response](https://github.com/openconfig/gnmi/blob/master/proto/gnmi/gnmi.proto#L440) per target.

docs/user_guide/configuration_intro.md

@@ -18,7 +18,9 @@ See [here](configuration_flags.md) for a complete list of the supported global a
 The Env variable names are inline with the flag names as well as the configuration hierarchy.
 
 See [here](configuration_env.md) for more details on environment variables.
+
 ## File configuration
+
 Configuration file that `gnmic` reads must be in one of the following formats: JSON, YAML, TOML, HCL or Properties.  
 
 By default, `gnmic` will search for a file named `.gnmic.[yml/yaml, toml, json]` in the following locations and will use the first file that exists: