docs: update markdownlint rules for better formatting

docs/networking/port-management.md

@@ -28,8 +28,7 @@ The proxy port scheme is as follows:
 
 - `SCHEME:HOST_PORT:CONTAINER_PORT`
 
-The scheme metadata can be used by proxy implementations in order to properly handle proxying of requests. For example, the built-in `nginx-vhosts` proxy implementation supports the `http`, `https`, `grpc` and `grpcs` schemes. 
-For the `grpc` and `grpcs` see [nginx blog post on grpc](https://www.nginx.com/blog/nginx-1-13-10-grpc/).
+The scheme metadata can be used by proxy implementations in order to properly handle proxying of requests. For example, the built-in `nginx-vhosts` proxy implementation supports the `http`, `https`, `grpc` and `grpcs` schemes. For the `grpc` and `grpcs` see [nginx blog post on grpc](https://www.nginx.com/blog/nginx-1-13-10-grpc/).
 
 Developers of proxy implementations are encouraged to use whatever schemes make the most sense, and ignore configurations which they do not support. For instance, a `udp` proxy implementation can safely ignore `http` and `https` port mappings.
 

docs/networking/proxies/nginx.md

@@ -107,7 +107,7 @@ Once the HSTS setting is disabled globally, it can be re-enabled on a per-app ba
 dokku nginx:set node-js-app hsts true
 ```
 
-### Running behind another proxy — configuring `X-Forwarded-*` headers:
+### Running behind another proxy — configuring `X-Forwarded-*` headers
 
 Dokku's default Nginx configuration passes the de-facto standard HTTP headers [`X-Forwarded-For`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For), [`X-Forwarded-Proto`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-Proto), and `X-Forwarded-Port` to your application.
 These headers indicate the IP address of the original client making the request, the protocol of the original request (HTTP or HTTPS), and the port number of the original request, respectively.
@@ -331,7 +331,6 @@ When deploying a monorepo, it may be desirable to specify the specific path of t
 
 For deploys via the `git:from-image` and `git:load-image` commands, the `nginx.conf.sigil` is extracted from the configured `WORKDIR` property of the image. For all other deploys - git push, `git:from-archive`, `git:sync` - will have the `nginx.conf.sigil` extracted directly from the source code. Both cases will respect the configured `nginx-conf-sigil-path` property value.
 
-
 ```shell
 dokku nginx:set node-js-app nginx-conf-sigil-path .dokku/nginx.conf.sigil
 ```

docs/networking/proxy-management.md

@@ -117,36 +117,36 @@ From Dokku versions `0.5.0` until `0.11.0`, enabling or disabling an application
 
 Custom plugins names _must_ have the suffix `-vhosts` or scheduler overriding via `proxy:set` may not function as expected.
 
-At this time, the following dokku commands are used to interact with a complete proxy implementation. 
+At this time, the following dokku commands are used to interact with a complete proxy implementation.
 
 - `domains:add`: Adds a given domain to an app.
-  - triggers: `post-domains-update`
+    - triggers: `post-domains-update`
 - `domains:clear`: Clears out an app's associated domains.
-  - triggers: `post-domains-update`
+    - triggers: `post-domains-update`
 - `domains:disable`: Disables domains for an app.
-  - triggers: `pre-disable-vhost`
+    - triggers: `pre-disable-vhost`
 - `domains:enable`: Enables domains for an app.
-  - triggers: `pre-enable-vhost`
+    - triggers: `pre-enable-vhost`
 - `domains:remove`: Removes a domain from an app.
-  - triggers: `post-domains-update`
+    - triggers: `post-domains-update`
 - `domains:set`: Sets all domains for a given app.
-  - triggers: `post-domains-update`
+    - triggers: `post-domains-update`
 - `proxy:build-config`: Builds - or rebuilds - external proxy configuration.
-  - triggers: `proxy-build-config`
+    - triggers: `proxy-build-config`
 - `proxy:clear-config`: Clears out external proxy configuration.
-  - triggers: `proxy-clear-config`
+    - triggers: `proxy-clear-config`
 - `proxy:disable`: Disables the proxy configuration for an app.
-  - triggers: `proxy-disable`
+    - triggers: `proxy-disable`
 - `proxy:enable`: Enables the proxy configuration for an app.
-  - triggers: `proxy-enable`
+    - triggers: `proxy-enable`
 - `ports:add`: Adds one or more port mappings to an app
-  - triggers: `post-proxy-ports-update`
+    - triggers: `post-proxy-ports-update`
 - `ports:clear`: Clears out all port mappings for an app.
-  - triggers: `post-proxy-ports-update`
+    - triggers: `post-proxy-ports-update`
 - `ports:remove`: Removes one or more port mappings from an app.
-  - triggers: `post-proxy-ports-update`
+    - triggers: `post-proxy-ports-update`
 - `ports:set`: Sets all port mappings for an app.
-  - triggers: `post-proxy-ports-update`
+    - triggers: `post-proxy-ports-update`
 
 Proxy implementations may decide to omit some functionality here, or use plugin triggers to supplement config with information from other plugins.