Fix .markdown extension links in openvox-server and openvoxdb docs

Inline links in _openvox-server_8x and _openvoxdb_8x used .markdown
extensions which Jekyll renders as .html. PR #119 fixed this in
_openvox_8x; this extends the same fix to the remaining two collections.

22 files updated across both collections.

Part of the link debt being surfaced by #120.

Signed-off-by: Michael Harp <mike@mikeharp.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: miharp

docs/_openvox-server_8x/config_file_auth.markdown

@@ -78,7 +78,7 @@ If this setting is `true`, Puppet Server ignores any presented certificate and r
 
 You cannot rename any of the `X-Client` headers when this setting is enabled, and you must specify identity through the `X-Client-Verify`, `X-Client-DN`, and `X-Client-Cert` headers.
 
-For more information, see [External SSL Termination](./external_ssl_termination.markdown#disable-https-for-puppet-server) in the Puppet Server documentation and
+For more information, see [External SSL Termination](./external_ssl_termination.html#disable-https-for-puppet-server) in the Puppet Server documentation and
 [Configuring the Authorization Service](https://github.com/puppetlabs/trapperkeeper-authorization/blob/master/doc/authorization-config.md#allow-header-cert-info) in the `trapperkeeper-authorization`
 documentation.
 

docs/_openvox-server_8x/config_file_auth_migration.markdown

@@ -41,25 +41,25 @@ The following rules, settings, and values have no direct equivalent in the new H
 
 The HOCON `auth.conf` file has some fundamental structural requirements:
 
-- An [`authorization`](./config_file_auth.markdown#authorization) section, which contains:
-  - A [`version`](./config_file_auth.markdown#version) setting.
-  - A [`rules`](./config_file_auth.markdown#rules) array of map values, each representing an authorization rule. Each rule must contain:
-    - A [`match-request`](./config_file_auth.markdown#match-request) section.
-      - Each `match-request` section must contain at least one [`path`](./config_file_auth.markdown#path) and [`type`](./config_file_auth.markdown#type).
-    - A numeric [`sort-order`](./config_file_auth.markdown#sort-order) value.
+- An [`authorization`](./config_file_auth.html#authorization) section, which contains:
+  - A [`version`](./config_file_auth.html#version) setting.
+  - A [`rules`](./config_file_auth.html#rules) array of map values, each representing an authorization rule. Each rule must contain:
+    - A [`match-request`](./config_file_auth.html#match-request) section.
+      - Each `match-request` section must contain at least one [`path`](./config_file_auth.html#path) and [`type`](./config_file_auth.html#type).
+    - A numeric [`sort-order`](./config_file_auth.html#sort-order) value.
       - If the value is between 1 and 399, the rule supersedes Puppet Server's default authorization rules.
       - If the value is between 601 and 998, the rule can be overridden by Puppet Server's default authorization rules.
-    - A string [`name`](./config_file_auth.markdown#name) value.
+    - A string [`name`](./config_file_auth.html#name) value.
     - At least one of the following:
-      - An [`allow` value, a `deny` value, or both](./config_file_auth.markdown#allow-allow-unauthenticated-and-deny). The `allow` or `deny` values can contain:
+      - An [`allow` value, a `deny` value, or both](./config_file_auth.html#allow-allow-unauthenticated-and-deny). The `allow` or `deny` values can contain:
         - A single string, representing the request's "name" derived from the Common Name (CN) attribute within an X.509 certificate's Subject Distinguished Name (DN). This string can be an exact name, a glob,
           or a regular expression.
         - A single map value containing an `extension` key.
         - A single map value containing a `certname` key.
         - An array of values, including string and map values.
-      - An [`allow-unauthenticated`](./config_file_auth.markdown#allow-allow-unauthenticated-and-deny) value, but if present, there cannot also be an `allow` value.
+      - An [`allow-unauthenticated`](./config_file_auth.html#allow-allow-unauthenticated-and-deny) value, but if present, there cannot also be an `allow` value.
 
-For an full example of a HOCON `auth.conf` file, see the [HOCON `auth.conf` documentation](./config_file_auth.markdown#hocon-example).
+For an full example of a HOCON `auth.conf` file, see the [HOCON `auth.conf` documentation](./config_file_auth.html#hocon-example).
 
 ### Converting a simple rule
 
@@ -92,7 +92,7 @@ authorization: {
 
 Next, let's convert each component of the deprecated rule to the new HOCON format.
 
-1. Add the path to the new rule's [`path`](./config_file_auth.markdown#match-request) setting in its `match-request` section.
+1. Add the path to the new rule's [`path`](./config_file_auth.html#match-request) setting in its `match-request` section.
 
    ```hocon
    ...
@@ -107,7 +107,7 @@ Next, let's convert each component of the deprecated rule to the new HOCON forma
    ...
    ```
 
-2. Next, add its type to the section's [`type`](./config_file_auth.markdown#match-request) setting. Because this is a literal string path, the type is `path`.
+2. Next, add its type to the section's [`type`](./config_file_auth.html#match-request) setting. Because this is a literal string path, the type is `path`.
 
    ```hocon
    ...
@@ -122,8 +122,8 @@ Next, let's convert each component of the deprecated rule to the new HOCON forma
    ...
    ```
 
-3. The legacy rule has a [`method`](./config_file_auth.markdown#method-1) setting, with an indirector value of `find` that's equivalent to the GET and POST HTTP methods. We can implement these by adding an
-   optional HOCON [`method`](./config_file_auth.markdown#match-request) setting in the rule's `match-request` section and specifying GET and POST as an array.
+3. The legacy rule has a [`method`](./config_file_auth.html#method-1) setting, with an indirector value of `find` that's equivalent to the GET and POST HTTP methods. We can implement these by adding an
+   optional HOCON [`method`](./config_file_auth.html#match-request) setting in the rule's `match-request` section and specifying GET and POST as an array.
 
    ```hocon
    ...

docs/_openvox-server_8x/crl_refresh.markdown

@@ -6,7 +6,7 @@ canonical: "/puppetserver/latest/crl_refresh.html"
 
 Starting in version 5.1.0, Puppet Server can automatically reload an updated CRL into the running SSL context, so that the revocation of an agent's certificate no longer requires a restart of the service to take effect. Prior versions required an explicit restart or reload of this service to reload the CRL, resulting in some small amount of downtime to effect the revocation of a certificate. Revocation is now transparent and requires no service downtime.
 
-If you are upgrading and have modified your ca.cfg, adding the following line manually may be required. See [Service Bootstraping](./configuration.markdown#service-bootstrapping) for information on how to update your Puppet Server's services bootstrap configuration.
+If you are upgrading and have modified your ca.cfg, adding the following line manually may be required. See [Service Bootstraping](./configuration.html#service-bootstrapping) for information on how to update your Puppet Server's services bootstrap configuration.
 
 `puppetlabs.trapperkeeper.services.watcher.filesystem-watch-service/filesystem-watch-service`
 

docs/_openvox-server_8x/gems.markdown

@@ -90,7 +90,7 @@ As an example, the following command installs `pry` locally in the project. Note
     Successfully installed pry-0.10.1-java
     5 gems installed
 
-With the gem installed into the project tree `pry` can be invoked from inside Ruby code. For more detailed information on `pry` see [Puppet Server: Debugging](./dev_debugging.markdown#pry).
+With the gem installed into the project tree `pry` can be invoked from inside Ruby code. For more detailed information on `pry` see [Puppet Server: Debugging](./dev_debugging.html#pry).
 
 ## Gems with Native (C) Extensions
 

docs/_openvox-server_8x/puppet_conf_setting_diffs.markdown

@@ -9,17 +9,17 @@ Puppet Server honors almost all settings in puppet.conf and should pick them up
 
 ## [`autoflush`](https://puppet.com/docs/puppet/latest/configuration.html#autoflush)
 
-Puppet Server does not use this setting. For more information on the master logging implementation for Puppet Server, see the [logging configuration section](./configuration.markdown#logging).
+Puppet Server does not use this setting. For more information on the master logging implementation for Puppet Server, see the [logging configuration section](./configuration.html#logging).
 
 ## [`bindaddress`](https://puppet.com/docs/puppet/latest/configuration.html#bindaddress)
 
 Puppet Server does not use this setting. To set the address on which the master listens, use either `host` (unencrypted) or `ssl-host` (SSL encrypted) in the
-[webserver.conf](./configuration.markdown#webserverconf) file.
+[webserver.conf](./configuration.html#webserverconf) file.
 
 ## [`ca`](https://puppet.com/docs/puppet/latest/configuration.html#ca)
 
 Puppet Server does not use this setting. Instead, Puppet Server acts as a certificate authority based on the certificate authority service configuration in the `ca.cfg` file. See
-[Service Bootstrapping](./configuration.markdown#service-bootstrapping) for more details.
+[Service Bootstrapping](./configuration.html#service-bootstrapping) for more details.
 
 ## [`ca_ttl`](https://puppet.com/docs/puppet/latest/configuration.html#cattl)
 
@@ -28,11 +28,11 @@ Puppet Server enforces a max ttl of 50 standard years (up to 1576800000 seconds)
 ## [`cacert`](https://puppet.com/docs/puppet/latest/configuration.html#cacert)
 
 If you enable Puppet Server's certificate authority service, it uses the `cacert` setting in puppet.conf to determine the location of the CA certificate for such tasks as generating the CA certificate or using
-the CA to sign client certificates. This is true regardless of the configuration of the `ssl-` settings in [webserver.conf](./configuration.markdown#webserverconf).
+the CA to sign client certificates. This is true regardless of the configuration of the `ssl-` settings in [webserver.conf](./configuration.html#webserverconf).
 
 ## [`cacrl`](https://puppet.com/docs/puppet/latest/configuration.html#cacrl)
 
-If you define `ssl-cert`, `ssl-key`, `ssl-ca-cert`, or `ssl-crl-path` in [webserver.conf](./configuration.markdown#webserverconf), Puppet Server uses the file at `ssl-crl-path` as the CRL for authenticating
+If you define `ssl-cert`, `ssl-key`, `ssl-ca-cert`, or `ssl-crl-path` in [webserver.conf](./configuration.html#webserverconf), Puppet Server uses the file at `ssl-crl-path` as the CRL for authenticating
 clients via SSL. If at least one of the `ssl-` settings in webserver.conf is set but `ssl-crl-path` is not set, Puppet Server will _not_ use a CRL to validate clients via SSL.
 
 If none of the `ssl-` settings in webserver.conf are set, Puppet Server uses the CRL file defined for the `hostcrl` setting---and not the file defined for the `cacrl` setting--in puppet.conf. At start time,
@@ -55,7 +55,7 @@ Puppet Server does not use this setting.
 
 ## [`hostcert`](https://puppet.com/docs/puppet/latest/configuration.html#hostcert)
 
-If you define `ssl-cert`, `ssl-key`, `ssl-ca-cert`, or `ssl-crl-path` in [webserver.conf](./configuration.markdown#webserverconf), Puppet Server presents the file at `ssl-cert` to clients as the server
+If you define `ssl-cert`, `ssl-key`, `ssl-ca-cert`, or `ssl-crl-path` in [webserver.conf](./configuration.html#webserverconf), Puppet Server presents the file at `ssl-cert` to clients as the server
 certificate via SSL.
 
 If at least one of the `ssl-` settings in webserver.conf is set but `ssl-cert` is not set, Puppet Server gives an error and shuts down at startup. If none of the `ssl-` settings in webserver.conf are set,
@@ -66,7 +66,7 @@ determine the location of the server host certificate to generate.
 
 ## [`hostcrl`](https://puppet.com/docs/puppet/latest/configuration.html#hostcrl)
 
-If you define `ssl-cert`, `ssl-key`, `ssl-ca-cert`, or `ssl-crl-path` in [webserver.conf](./configuration.markdown#webserverconf), Puppet Server uses the file at `ssl-crl-path` as the CRL for authenticating
+If you define `ssl-cert`, `ssl-key`, `ssl-ca-cert`, or `ssl-crl-path` in [webserver.conf](./configuration.html#webserverconf), Puppet Server uses the file at `ssl-crl-path` as the CRL for authenticating
 clients via SSL. If at least one of the `ssl-` settings in webserver.conf is set but `ssl-crl-path` is not set, Puppet Server will _not_ use a CRL to validate clients via SSL.
 
 If none of the `ssl-` settings in webserver.conf are set, Puppet Server uses the CRL file defined for the `hostcrl` setting---and not the file defined for the `cacrl` setting--in puppet.conf. At start time,
@@ -77,7 +77,7 @@ the CRL. This is true regardless of the `ssl-` settings in webserver.conf.
 
 ## [`hostprivkey`](https://puppet.com/docs/puppet/latest/configuration.html#hostprivkey)
 
-If you define `ssl-cert`, `ssl-key`, `ssl-ca-cert`, or `ssl-crl-path` in [webserver.conf](./configuration.markdown#webserverconf), Puppet Server uses the file at `ssl-key` as the server private key during SSL
+If you define `ssl-cert`, `ssl-key`, `ssl-ca-cert`, or `ssl-crl-path` in [webserver.conf](./configuration.html#webserverconf), Puppet Server uses the file at `ssl-key` as the server private key during SSL
 transactions.
 
 If at least one of the `ssl-` settings in webserver.conf is set but `ssl-key` is not, Puppet Server gives an error and shuts down at startup. If none of the `ssl-` settings in webserver.conf are set, Puppet
@@ -89,40 +89,40 @@ regardless of the configuration of the `ssl-` settings in webserver.conf.
 ## [`http_debug`](https://puppet.com/docs/puppet/latest/configuration.html#httpdebug)
 
 Puppet Server does not use this setting. Debugging for HTTP client code in the Puppet Server master is controlled through Puppet Server's common logging mechanism. For more information on the master logging
-implementation for Puppet Server, see the [logging configuration section](./configuration.markdown#logging).
+implementation for Puppet Server, see the [logging configuration section](./configuration.html#logging).
 
 ## [`keylength`](https://puppet.com/docs/puppet/latest/configuration.html#keylength)
 
 Puppet Server does not currently use this setting. Puppet Server's certificate authority generates 4096-bit keys in conjunction with any SSL certificates that it generates.
 
 ## [`localcacert`](https://puppet.com/docs/puppet/latest/configuration.html#localcacert)
 
-If you define `ssl-cert`, `ssl-key`, `ssl-ca-cert`, and/or `ssl-crl-path` in [webserver.conf](./configuration.markdown#webserverconf), Puppet Server uses the file at `ssl-ca-cert` as the CA cert store for
+If you define `ssl-cert`, `ssl-key`, `ssl-ca-cert`, and/or `ssl-crl-path` in [webserver.conf](./configuration.html#webserverconf), Puppet Server uses the file at `ssl-ca-cert` as the CA cert store for
 authenticating clients via SSL.
 
 If at least one of the `ssl-` settings in webserver.conf is set but `ssl-ca-cert` is not set, Puppet Server gives an error and shuts down at startup. If none of the `ssl-` settings in webserver.conf is set,
 Puppet Server uses the CA file defined for the `localcacert` setting in puppet.conf for SSL authentication.
 
 ## [`logdir`](https://puppet.com/docs/puppet/latest/configuration.html#logdir)
 
-Puppet Server does not use this setting. For more information on the master logging implementation for Puppet Server, see the [logging configuration section](./configuration.markdown#logging).
+Puppet Server does not use this setting. For more information on the master logging implementation for Puppet Server, see the [logging configuration section](./configuration.html#logging).
 
 ## [`masterhttplog`](https://puppet.com/docs/puppet/latest/configuration.html#masterhttplog)
 
-Puppet Server does not use this setting. You can configure a web server access log via the `access-log-config` setting in the [webserver.conf](./configuration.markdown#webserverconf) file.
+Puppet Server does not use this setting. You can configure a web server access log via the `access-log-config` setting in the [webserver.conf](./configuration.html#webserverconf) file.
 
 ## [`masterlog`](https://puppet.com/docs/puppet/latest/configuration.html#masterlog)
 
-Puppet Server does not use this setting. For more information on the master logging implementation for Puppet Server, see the [logging configuration section](./configuration.markdown#logging).
+Puppet Server does not use this setting. For more information on the master logging implementation for Puppet Server, see the [logging configuration section](./configuration.html#logging).
 
 ## [`masterport`](https://puppet.com/docs/puppet/latest/configuration.html#masterport)
 
 Puppet Server does not use this setting. To set the port on which the master listens, set the `port` (unencrypted) or `ssl-port` (SSL encrypted) setting in the
-[webserver.conf](./configuration.markdown#webserverconf) file.
+[webserver.conf](./configuration.html#webserverconf) file.
 
 ## [`puppetdlog`](https://puppet.com/docs/puppet/latest/configuration.html#puppetdlog)
 
-Puppet Server does not use this setting. For more information on the master logging implementation for Puppet Server, see the [logging configuration section](./configuration.markdown#logging).
+Puppet Server does not use this setting. For more information on the master logging implementation for Puppet Server, see the [logging configuration section](./configuration.html#logging).
 
 ## [`rails_loglevel`](https://puppet.com/docs/puppet/latest/configuration.html#railsloglevel)
 
@@ -174,7 +174,7 @@ requests that the master would make to the `reporturl` for the `http` report pro
 
 ## Overriding Puppet settings in Puppet Server
 
-Currently, the [`jruby-puppet` section of your `puppetserver.conf` file](./configuration.markdown#puppetserver.conf) contains five settings (`master-conf-dir`, `master-code-dir`, `master-var-dir`,
+Currently, the [`jruby-puppet` section of your `puppetserver.conf` file](./configuration.html#puppetserver.conf) contains five settings (`master-conf-dir`, `master-code-dir`, `master-var-dir`,
 `master-run-dir`, and `master-log-dir`) that allow you to override settings set in your `puppet.conf` file. On installation, these five settings will be set to the proper default values.
 
 While you are free to change these settings at will, please note that any changes made to the `master-conf-dir` and `master-code-dir` settings absolutely MUST be made to the corresponding Puppet settings