docs: update markdownlint rules for better formatting

docs/processes/process-management.md

@@ -117,7 +117,7 @@ If the file exists, it should not be empty, as doing so may result in a failed d
 
 The syntax for declaring a `Procfile` is as follows. Note that the format is one process type per line, with no duplicate process types.
 
-```
+```Procfile
 <process type>: <command>
 ```
 
@@ -141,7 +141,7 @@ For initial app deploys, Dokku will default to starting a single `web` process f
 There are also a few other exceptions for the `web` process.
 
 - By default, the built-in nginx proxy implementation only proxies the `web` process (others may be handled via a custom `nginx.conf.sigil`).
-  - See the [nginx request proxying documentation](/docs/networking/proxies/nginx.md#request-proxying) for more information on how nginx handles proxied requests.
+    - See the [nginx request proxying documentation](/docs/networking/proxies/nginx.md#request-proxying) for more information on how nginx handles proxied requests.
 - Only the `web` process may be bound to an external port.
 
 #### The `release` process
@@ -206,7 +206,7 @@ dokku ps:scale --skip-deploy node-js-app web=1
 
 Users can also configure scaling within the codebase itself to manage process scaling. The `formation` key should be specified as follows in the `app.json` file:
 
-```Procfile
+```json
 {
   "formation": {
     "web": {
@@ -383,7 +383,7 @@ When a server reboots or Docker is restarted/upgraded, Docker may or may not sta
 - Start all linked services.
 - Clear generated proxy configuration files.
 - Start the app if it has not been manually stopped.
-  - If the app containers still exist, they will be started and the generated proxy configuration files will be rebuilt.
-  - If any of the app containers are missing, the entire app will be rebuilt.
+    - If the app containers still exist, they will be started and the generated proxy configuration files will be rebuilt.
+    - If any of the app containers are missing, the entire app will be rebuilt.
 
 During this time, requests may route to the incorrect app if the assigned IPs correspond to those for other apps. While dokku makes all efforts to avoid this, there may be a few minutes where urls may route to the wrong app. To avoid this, either use a custom proxy plugin or wait a few minutes until the restoration process is complete.

docs/processes/scheduled-cron-tasks.md

@@ -18,7 +18,7 @@ Dokku automates scheduled `dokku run` commands via it's `app.json` cron integrat
 
 The `app.json` file for a given app can define a special `cron` key that contains a list of commands to run on given schedules. The following is a simple example `app.json` that effectively runs the command `dokku run $APP npm run send-email` once a day:
 
-```
+```json
 {
   "cron": [
     {
@@ -168,8 +168,7 @@ For tasks that will properly resume, you _should_ use the above method, as runni
 Regularly scheduled tasks can be a bit of a pain with Dokku. The following are general recommendations to follow to help ensure successful task runs.
 
 - Use the `dokku` user in your cron entry.
-  - If you do not, the `dokku` binary will attempt to execute with `sudo`, and your cron run with fail with `sudo: no tty present and no askpass program specified`.
-
+    - If you do not, the `dokku` binary will attempt to execute with `sudo`, and your cron run with fail with `sudo: no tty present and no askpass program specified`.
 - Add a `MAILTO` environment variable to ship cron emails to yourself.
 - Add a `PATH` environment variable or specify the full path to binaries on the host.
 - Add a `SHELL` environment variable to specify Bash when running commands.