docs: fixes

Author: JTorreG

content/unit/howto/certbot.md

@@ -16,7 +16,7 @@ The commands in this document starting with a hash (#) must be run as root or
 with superuser privileges.
 {{< /note >}}
 
-## Generating Certificates
+## Generating certificates
 
 1. Install [Unit]({{< relref "/unit/installation.md#installation-precomp-pkgs" >}}) on your website's server.
 
@@ -155,7 +155,7 @@ with superuser privileges.
          ...
    ```
 
-## Renewing Certificates
+## Renewing certificates
 
 Certbot enables renewing the certificates [manually](https://eff-certbot.readthedocs.io/en/stable/using.html#renewing-certificates)
 or [automatically](https://eff-certbot.readthedocs.io/en/stable/using.html#automated-renewals).

content/unit/howto/docker.md

@@ -53,7 +53,7 @@ also, see a more elaborate discussion
 
 Now for a few detailed scenarios.
 
-## Apps in a Containerized Unit {#docker-apps-containerized-unit}
+## Apps in a containerized Unit {#docker-apps-containerized-unit}
 
 Suppose we have a web app with a few dependencies, say
 [Flask`s]({{< relref "/unit/howto/frameworks/flask.md" >}}) official **hello, world** app:
@@ -243,7 +243,7 @@ $ export UNIT=$(                                                         \
 ```
 
 
-## Containerized Apps {#docker-apps}
+## Containerized apps {#docker-apps}
 
 Suppose you have a Unit-ready
 [Express]({{< relref "/unit/howto/frameworks/express.md" >}})
@@ -399,7 +399,7 @@ $ docker exec -ti $UNIT curl -X PUT -d '"/www/newapp/"'  \
 This approach is applicable to any Unit-supported apps with external
 dependencies.
 
-## Multilanguage Images {#docker-multi}
+## Multilanguage images {#docker-multi}
 
 Earlier, Unit had a **-full** Docker image with modules for all supported
 languages, but it was discontinued with version 1.22.0. If you still need a
@@ -442,7 +442,7 @@ Instead of packages, you can build custom
 [modules]({{< relref "/unit/howto/source.md#source-modules" >}});
 use these **Dockerfile.\*** [templates](https://github.com/nginx/unit/tree/master/pkg/docker) as reference.
 
-## Startup Customization {#docker-startup}
+## Startup customization {#docker-startup}
 
 Finally, you can customize the way Unit starts in a container by adding a new
 Dockerfile layer:

content/unit/howto/integration.md

@@ -1,5 +1,5 @@
 ---
-title: NGINX Integration
+title: NGINX integration
 toc: true
 weight: 500
 ---
@@ -74,7 +74,7 @@ listener's **client_ip** option.
 For details, see the [NGINX documentation](https://nginx.org). Commercial
 support and advanced features are [also available](https://www.nginx.com).
 
-## Securely Proxying Unit's Control API {#nginx-secure-api}
+## Securely proxying Unit's control API {#nginx-secure-api}
 
 By default, Unit exposes its
 [control API]({{< relref "/unit/controlapi.md#configuration-mgmt" >}})

content/unit/howto/modules.md

@@ -1,5 +1,5 @@
 ---
-title: Working With Language Modules
+title: Working with language modules
 weight: 700
 toc: true
 ---
@@ -20,7 +20,7 @@ The commands in this document starting with a hash (#) must be run as root or
 with superuser privileges.
 {{< /note >}}
 
-## External Language Modules {#modules-ext}
+## External language modules {#modules-ext}
 
 External modules are regular language libraries or packages that you install
 like any other. They provide common web functionality, communicating with Unit
@@ -44,7 +44,7 @@ For WebAssembly, Unit delegates bytecode execution to the
 module or during a
 [source build]({{< relref "/unit/howto/source.md#source-wasm" >}}).
 
-## Embedded Language Modules {#modules-emb}
+## Embedded language modules {#modules-emb}
 
 Embedded modules are shared libraries that Unit loads at startup. Query Unit
 to find them in your system:

content/unit/howto/security.md

@@ -17,7 +17,7 @@ The commands in this document starting with a hash (#) must be run as root or
 with superuser privileges.
 {{< /note >}}
 
-## Update Unit Regularly {#security-update}
+## Update Unit regularly {#security-update}
 
 **Rationale**: Each release introduces [bug fixes and new
 features]({{< relref "/unit/changes.md" >}}) that improve your installation's security.
@@ -49,7 +49,7 @@ Specific upgrade steps depend on your installation method:
 
 </details>
 
-## Secure Socket and State {#security-socket-state}
+## Secure socket and state {#security-socket-state}
 
 **Rationale**: Your
 [control socket and state directory]({{< relref "/unit/howto/source.md#source-dir" >}})
@@ -189,7 +189,7 @@ configure SSL certificate bundles for your Unit installation.
 
 **Actions**: For details, see [SSL/TLS configuration]({{< relref "/unit/certificates.md#configuration-ssl" >}}) and [TLS with certbot]({{< relref "/unit/howto/certbot.md" >}}).
 
-## Error-Proof Your Routes {#security-routes}
+## Error-proof your routes {#security-routes}
 
 **Rationale**: Arguably, [routes]({{< relref "/unit/configuration.md#configuration-routes" >}})
 are the most flexible and versatile part of the Unit configuration. Thus, they must be as
@@ -227,7 +227,7 @@ Some considerations:
 
 </details>
 
-## Protect App Data {#security-apps}
+## Protect app data {#security-apps}
 
 **Rationale**: Unit's architecture involves many processes that operate
 together during app delivery; improper process permissions can make sensitive
@@ -649,7 +649,7 @@ shared during routing.
 
 </details>
 
-## Prune Debug and Access Logs {#security-logs}
+## Prune debug and access logs {#security-logs}
 
 **Rationale**: Unit stores potentially sensitive data in its general and access
 logs; their size can also become a concern if debug mode is enabled.
@@ -753,7 +753,7 @@ ACLs.
 
 </details>
 
-## Add Restrictions, Isolation {#security-isolation}
+## Add restrictions, isolation {#security-isolation}
 
 **Rationale**: If the underlying OS allows, Unit provides features that create an
 additional level of separation and containment for your apps, such as:

content/unit/howto/source.md

@@ -379,7 +379,6 @@ or support for certain features:
 {{</bootstrap-table>}}
 
 
-(source-config-src-pcre)=
 <a name="source-config-src-pcre"></a>
 
 By default, Unit relies on the locally installed version of the [PCRE](https://www.pcre.org) library to support regular expressions in

content/unit/news/2024/wasm-component-model-part-2.md

@@ -56,7 +56,7 @@ For more information about Wasmtime and installing it, see their [GitHub reposit
 
 Once we have all the tools in place, we can create the Rust projects.
 
-(tutorial-rust-based-wasm-component)=
+<a name="tutorial-rust-based-wasm-component"></a>
 
 ### Using the **wasi** Rust library
 

content/unit/statusapi.md

@@ -70,6 +70,10 @@ Example:
 }
 ```
 
+---
+
+## Modules
+
 Each item in the **modules** object lists one of the currently loaded language
 modules, the installed version (or versions) of the module, and the path to the
 module file:
@@ -84,6 +88,9 @@ module file:
 
 {{</bootstrap-table>}}
 
+---
+
+## Connections
 
 The **connections** object offers the following Unit instance metrics:
 
@@ -98,8 +105,6 @@ The **connections** object offers the following Unit instance metrics:
 
 {{</bootstrap-table>}}
 
-
-
 Example:
 
 ```json
@@ -117,6 +122,9 @@ refer to
 [Configuration Settings]({{< relref "/unit/configuration.md#configuration-stngs" >}}).
 {{< /note >}}
 
+---
+
+## Requests
 
 The **requests** object currently exposes a single instance-wide metric:
 
@@ -128,8 +136,6 @@ The **requests** object currently exposes a single instance-wide metric:
 
 {{</bootstrap-table>}}
 
-
-
 Example:
 
 ```json
@@ -138,6 +144,10 @@ Example:
 }
 ```
 
+---
+
+## Applications
+
 Each item in **applications** describes an app currently listed in the
 **/config/applications**
 [section]({{< relref "/unit/configuration.md#configuration-applications" >}}).
@@ -151,8 +161,6 @@ Each item in **applications** describes an app currently listed in the
 
 {{</bootstrap-table>}}
 
-
-
 Example:
 
 ```json
@@ -171,6 +179,10 @@ Example:
 }
 ```
 
+---
+
+## Processes
+
 The **processes** object exposes the following per-app metrics:
 
 {{<bootstrap-table "table table-striped table-bordered">}}

content/unit/troubleshooting.md

@@ -90,7 +90,7 @@ the [control API]({{< relref "/unit/controlapi.md" >}}) for details:
 curl --unix-socket /path/to/control.unit.sock http://localhost/config/routes/2  # The step listed in the log
 ```
 
-### Debug Events {#troubleshooting-dbg-log}
+### Debug events {#troubleshooting-dbg-log}
 
 Unit's log can be set to record **[debug]**-level events; the steps to enable this
 mode vary by install method.
@@ -150,7 +150,7 @@ Then recompile and reinstall Unit and your
 {{< /tabs >}}
 
 
-## Core Dumps {#troubleshooting-core-dumps}
+## Core dumps {#troubleshooting-core-dumps}
 
 Core dumps help us investigate crashes; attach them when
 [reporting an issue]({{< relref "/unit/troubleshooting.md#troubleshooting-support" >}}).
@@ -308,7 +308,7 @@ After a crash, locate the core dump file:
 {{% /tab %}}
 {{< /tabs >}}
 
-## Getting Support {#troubleshooting-support}
+## Getting support {#troubleshooting-support}
 
 {{<bootstrap-table "table table-striped table-bordered">}}