docs: update markdownlint rules for better formatting

docs/getting-started/advanced-installation.md

@@ -78,7 +78,7 @@ Follow the [user management documentation](/docs/deployment/user-management.md)
 
 ## VMs with less than 1 GB of memory
 
-Having less than 1 GB of system memory available for Dokku and its containers may result in unexpected errors, such as `! [remote rejected] master -> master (pre-receive hook declined)` during installation of NPM dependencies (https://github.com/npm/npm/issues/3867).
+Having less than 1 GB of system memory available for Dokku and its containers may result in unexpected errors, such as `! [remote rejected] master -> master (pre-receive hook declined)` [during installation of NPM dependencies](https://github.com/npm/npm/issues/3867).
 
 To work around this issue, it might suffice to augment the Linux swap file size to a maximum of twice the physical memory size.
 

docs/getting-started/install/vagrant.md

@@ -36,7 +36,7 @@
         Port 22
     ```
 
-    > For users that have customized the IP address of their VM - either in a custom `Vagrantfile` or via the `DOKKU_IP` environment variable - and are not using `10.0.0.2` for the Vagrant IP, you'll need to instead use the output of `vagrant ssh-config dokku` for your `~/.ssh/config` entry. 
+    > For users that have customized the IP address of their VM - either in a custom `Vagrantfile` or via the `DOKKU_IP` environment variable - and are not using `10.0.0.2` for the Vagrant IP, you'll need to instead use the output of `vagrant ssh-config dokku` for your `~/.ssh/config` entry.
 
 6. Connect to the server via `vagrant ssh` and add your ssh key to the install. Additionally, set the global domain name to `dokku.me`.
 

docs/getting-started/installation/index.md

@@ -1,10 +1,10 @@
 # Getting Started with Dokku
 
-### What is Dokku?
+## What is Dokku?
 
 Dokku is an extensible, open source Platform as a Service that runs on a single server of your choice. Dokku supports building apps on the fly from a `git push` via either Dockerfile or by auto-detecting the language with Buildpacks, and then starts containers based on your built image. Using technologies such as nginx and cron, Web processes are automatically routed to, while background processes and automated cron tasks are also managed by Dokku.
 
-### System Requirements
+## System Requirements
 
 To start using Dokku, you'll need a system that meets the following minimum requirements:
 
@@ -12,7 +12,7 @@ To start using Dokku, you'll need a system that meets the following minimum requ
     - [Ubuntu 20.04/22.04](https://www.ubuntu.com/download)
     - [Debian 10+ x64](https://www.debian.org/distrib/)
 - A server with one of the following architectures
-    - AMD64 (alternatively known as `x86_64`), commonly used for Intel cloud servers 
+    - AMD64 (alternatively known as `x86_64`), commonly used for Intel cloud servers
     - ARMV7 (alternatively known as `armhf`), commonly used for Raspberry PI
     - ARMV8 (alternatively known as `arm64`), commonly used for Raspberry PI and AWS Graviton
 
@@ -28,11 +28,11 @@ Finally, we recommend attaching at least one domain name to your server. This is
 
 Please see the [dns documentation](/docs/networking/dns.md) and [domains documentation](/docs/configuration/domains.md) for more details.
 
-### Installing the latest stable version
+## Installing the latest stable version
 
-This is the simple method of installing Dokku. For alternative methods of installation, see the [advanced install guide](/docs/getting-started/advanced-installation.md#configuring). 
+This is the simple method of installing Dokku. For alternative methods of installation, see the [advanced install guide](/docs/getting-started/advanced-installation.md#configuring).
 
-#### 1. Install Dokku
+### 1. Install Dokku
 
 To install the latest stable version of Dokku, you can run the following shell commands:
 
@@ -44,7 +44,7 @@ sudo DOKKU_TAG=v0.31.0 bash bootstrap.sh
 
 The installation process takes about 5-10 minutes, depending upon internet connection speed.
 
-#### 2. Setup SSH key and Virtualhost Settings
+### 2. Setup SSH key and Virtualhost Settings
 
 Once the installation is complete, you should configure an ssh key and set your global domain.
 
@@ -67,6 +67,6 @@ dokku domains:set-global 10.0.0.2.sslip.io
 
 See the [user management](/docs/deployment/user-management.md#adding-ssh-keys) and [domains documentation](/docs/configuration/domains.md#customizing-hostnames) for more information.
 
-#### 3. Deploy your first application
+### 3. Deploy your first application
 
 At this point, you should be able to [deploy to the Dokku installation](/docs/deployment/application-deployment.md).

docs/getting-started/troubleshooting.md

@@ -33,7 +33,7 @@ dokku trace:off
 
 ## Common Problems
 
-### I deployed my app but I am getting the default nginx page.
+### I deployed my app but I am getting the default nginx page
 
 Most of the time it's caused by some defaults newer versions of nginx set. To make sure that's the issue you're having run the following:
 
@@ -91,7 +91,7 @@ The following error may be emitted from a deploy:
 
 The `remote rejected` error does not give enough information. Anything could have failed. Enable trace mode and begin debugging. If this does not help you, create a [gist](https://gist.github.com) containing the full log, and create an issue.
 
-One the reasons why you may get this error is because the command that is run in the container exited (without errors). For example, (in Procfile) when you define a new worker container to run Delayed Job and use the bin/delayed_job start command. This command deamonizes the process and exists. The container thinks it's done so it closes itself. The error you get is the one above. To fix the above problem for Delayed Job, you must define the worker to user rake jobs:work, which doesn't deamonize the process. 
+One the reasons why you may get this error is because the command that is run in the container exited (without errors). For example, (in Procfile) when you define a new worker container to run Delayed Job and use the bin/delayed_job start command. This command deamonizes the process and exists. The container thinks it's done so it closes itself. The error you get is the one above. To fix the above problem for Delayed Job, you must define the worker to user rake jobs:work, which doesn't deamonize the process.
 
 ### I get the aforementioned error in the build phase (after turning on Dokku tracing)
 
@@ -121,7 +121,7 @@ Sometimes (especially on DigitalOcean) deploying again seems to get past these s
 resolvconf -u
 ```
 
-Please see https://github.com/dokku/dokku/issues/841 and https://github.com/dokku/dokku/issues/649.
+Please see [#841](https://github.com/dokku/dokku/issues/841) and [#649](https://github.com/dokku/dokku/issues/649).
 
 ### After adding an SSH key, I am told I cannot read from the remote repository on push
 
@@ -155,7 +155,7 @@ Host DOKKU_HOSTNAME
 
 Also see [issue #116](https://github.com/dokku/dokku/issues/116).
 
-### I successfully deployed my application with no deployment errors and receiving **Bad Gateway** when attempting to access the application.
+### I successfully deployed my application with no deployment errors and receiving **Bad Gateway** when attempting to access the application
 
 In many cases the application will require the a `process.env.PORT` port opposed to a specified port.
 
@@ -171,7 +171,7 @@ Additionally, your application should listen/bind to all interfaces (`0.0.0.0`).
 
 Please see [#5798](https://github.com/dokku/dokku/issues/5798).
 
-### Deployment fails because of slow internet connection, messages shows `gzip: stdin: unexpected end of file`.
+### Deployment fails because of slow internet connection, messages shows `gzip: stdin: unexpected end of file`
 
 If you see output similar this when deploying:
 
@@ -191,11 +191,11 @@ dokku config:set --global CURL_TIMEOUT=1200
 dokku config:set --global CURL_CONNECT_TIMEOUT=180
 ```
 
-Please see https://github.com/dokku/dokku/issues/509.
+Please see [#509](https://github.com/dokku/dokku/issues/509).
 
 Another reason for this error (although it may respond immediately ruling out a timeout issue) may be because you've set the config setting `SSL_CERT_FILE`. Using a config setting with this key interferes with the buildpack's ability to download its dependencies, so you must rename the config setting to something else, e.g. `MY_APP_SSL_CERT_FILE`.
 
-### Build fails with `Killed` message.
+### Build fails with `Killed` message
 
 This generally occurs when the server runs out of memory. You can either add more RAM to your server or setup swap space. The follow script will create 2 GB of swap space.
 
@@ -209,7 +209,7 @@ sudo sysctl -w vm.swappiness=10
 echo vm.swappiness = 10 | sudo tee -a /etc/sysctl.conf
 ```
 
-### I successfully deployed my application with no deployment errors but I'm receiving Connection Timeout when attempting to access the application.
+### I successfully deployed my application with no deployment errors but I'm receiving Connection Timeout when attempting to access the application
 
 This can occur if Dokku is running on a system with a firewall like UFW enabled (some OS versions like Ubuntu have this enabled by default). You can check if this is your case by running the following script:
 
@@ -223,7 +223,7 @@ If the previous script returned `Status: active` and a list of ports, UFW is ena
 sudo ufw disable
 ```
 
-### I can't connect to my application because the server is sending an invalid response, or can't provide a secure connection.
+### I can't connect to my application because the server is sending an invalid response, or can't provide a secure connection
 
 This isn't usually an issue with Dokku, but rather an app config problem. This can happen when your application is configured to enforce secure connections/HSTS, but you don't have SSL set up for the app.