PS-10076 [DOCS] Fix broken links in doc project (#537)

modified:   docs/data-loading.md
	modified:   docs/data-masking-function-list.md
	modified:   docs/data-masking-overview.md
	modified:   docs/encrypting-doublewrite-buffers.md
	modified:   docs/encryption-functions-overview.md
	modified:   docs/encryption-functions.md
	modified:   docs/enforce-engine.md
	modified:   docs/index-info-schema-tables.md
	modified:   docs/install-myrocks.md
	modified:   docs/jemalloc-profiling.md
	modified:   docs/ldap-authentication.md
	modified:   docs/limitations.md
	modified:   docs/myrocks-performance-schema-tables.md
	modified:   docs/post-installation.md
	modified:   docs/procfs-plugin.md
	modified:   docs/quickstart-apt.md
	modified:   docs/release-notes/8.0.31-23.md
	modified:   docs/release-notes/8.0.42-33.md
	modified:   docs/upgrade-percona-repos.md
	modified:   docs/utility-user.md
	modified:   docs/variables.md
	modified:   docs/zenfs.md

Author: alina-derkach-oaza

docs/data-loading.md

@@ -121,7 +121,7 @@ need to truncate the table and loading data again.
 
 !!! warning
 
-    If you are loading large data without enabling [rocksdb_bulk_load](variables.md#rocksdb_bulk_load) or [rocksdb_commit_in_the_middle](variables.md#rocksdb-commit-in-the-middle), please make sure transaction size is small enough. All modifications of the ongoing transactions are kept in memory.
+If you are loading large data without enabling [rocksdb_bulk_load](variables.md#rocksdb_bulk_load) or [rocksdb_commit_in_the_middle](variables.md#rocksdb_commit_in_the_middle), please make sure transaction size is small enough. All modifications of the ongoing transactions are kept in memory.
 
 ## Other reading
 

docs/data-masking-function-list.md

@@ -963,7 +963,7 @@ mysql> SELECT masking_dictionary_term_remove('trees','pine');
 | **Name**                                          | **Details**                                             |
 |---------------------------------------------------|-------------------------------------------------------|
 | [`dictionaries_flush_interval_seconds (integer, unsigned)`](#dictionaries_flush_interval_secondsinteger-unsigned) | The number of seconds between updates to the internal dictionary cache to match changes in the dictionaries table.|
-| [`masking_database(str)`](#masking_databasestr) | Set a different database name to use for the dictionaries table. |
+| [`masking_database(string)`](#masking_databasestring) | Set a different database name to use for the dictionaries table. |
 
 ### dictionaries_flush_interval_seconds(integer, unsigned)
 

docs/data-masking-overview.md

@@ -39,7 +39,7 @@ To fix this, you can use the new [`masking_dictionaries_flush()`](data-masking-f
 
 The changes also affect how row-based replication works. When dictionary changes happen on the source server, they travel through the binary log to the replica server. While the replica applies these changes to its table correctly, the dictionary term cache doesn't update right away.
 
-To handle this, there's a new system setting called  [`component_masking_functions.dictionaries_flush_interval_seconds()`](data-masking-function-list.html#dictionaries_flush_interval_secondsinteger-unsigned)
+To handle this, there's a new system setting called  [`component_masking_functions.dictionaries_flush_interval_seconds()`](data-masking-function-list.md#dictionaries_flush_interval_secondsinteger-unsigned)
 
 By default, it's set to 0. When you set it higher, the system starts a background process that refreshes the cache at your specified interval. This helps replicas stay in sync after receiving binary log updates. The value specifies the number of seconds between each sync. 
 

docs/encrypting-doublewrite-buffers.md

@@ -5,8 +5,8 @@ A summary of Doublewrite buffer and Doublewrite buffer encryption changes:
 |_Percona Server for MySQL_ Versions| Doublewrite Buffer and Doublewrite Buffer Encryption Implementation|
 |---|---|
 |Percona Server from Percona-Server-8.0.23-14|_MySQL_ 8.0.23 implemented its own version of [parallel doublewrite encryption](https://dev.mysql.com/doc/refman/8.0/en/innodb-data-encryption.html#innodb-doublewrite-file-encryption). Pages that belong to encrypted tablespaces are also written into the doublewrite buffer in an encrypted form. The Percona implementation was reverted and the[innodb_parallel_dblwr_encrypt](#innodb_parallel_dblwr_encrypt) is deprecated and may be removed in later releases.
-|Percona Server from Percona-Server-8.0.20-11 to Percona-Server-8.0.22-13 inclusive|_MySQL_ 8.0.20 implemented its own [parallel doublewrite buffer](https://dev.mysql.com/doc/refman/8.0/en/innodb-doublewrite-buffer.html), which is stored in external files (#ib\_16384\_xxx.dblwr) and not stored in the system tablespace. Percona’s implementation was reverted. As a result, [innodb\_parallel\_doublewrite\_path](xtradb-performance-improvements-io-bound-highly-concurrent-workloads.md#innodb-parallel-doublewrite-path) was deprecated. <br> However, _MySQL_ did not implement parallel doublewrite buffer encryption at this time, so Percona reimplemented parallel doublewrite buffer encryption on top of the _MySQL_ parallel doublewrite buffer implementation. Percona preserved the meaning and functionality of the [innodb\_parallel\_dblwr\_encrypt](#innodb_parallel_dblwr_encrypt) variable. |
-|Percona-Server-8.0.12-1.alpha to Percona-Server-8.0.19-10 inclusive|_Percona Server for MySQL_ had its own implementation of the parallel doublewrite buffer which was enabled by setting the [innodb\_parallel\_doublewrite\_path](xtradb-performance-improvements-io-bound-highly-concurrent-workloads.md#innodb-parallel-doublewrite-path) variable. <br> Enabling the [innodb\_parallel\_dblwr\_encrypt](#innodbparalleldblwrencrypt) controlled whether the parallel doublewrite pages were encrypted or not. In case the parallel doublewrite buffer was disabled ([innodb\_parallel\_doublewrite\_path](xtradb-performance-improvements-io-bound-highly-concurrent-workloads.md#innodb-parallel-doublewrite-path) was set to empty string),the doublewrite buffer pages were located in the system tablespace (ibdata1). The system tablespace itself could be encrypted by setting [innodb\_sys\_tablespace\_encrypt](encrypting-system-tablespace.md#innodb-sys-tablespace-encrypt), which also encrypted the doublewrite buffer pages.|
+|Percona Server from Percona-Server-8.0.20-11 to Percona-Server-8.0.22-13 inclusive|_MySQL_ 8.0.20 implemented its own [parallel doublewrite buffer](https://dev.mysql.com/doc/refman/8.0/en/innodb-doublewrite-buffer.html), which is stored in external files (#ib\_16384\_xxx.dblwr) and not stored in the system tablespace. Percona’s implementation was reverted. As a result, [innodb\_parallel\_doublewrite\_path](xtradb-performance-improvements-io-bound-highly-concurrent-workloads.md#innodb_parallel_doublewrite_path) was deprecated. <br> However, _MySQL_ did not implement parallel doublewrite buffer encryption at this time, so Percona reimplemented parallel doublewrite buffer encryption on top of the _MySQL_ parallel doublewrite buffer implementation. Percona preserved the meaning and functionality of the [innodb\_parallel\_dblwr\_encrypt](#innodb_parallel_dblwr_encrypt) variable. |
+|Percona-Server-8.0.12-1.alpha to Percona-Server-8.0.19-10 inclusive|_Percona Server for MySQL_ had its own implementation of the parallel doublewrite buffer which was enabled by setting the [innodb\_parallel\_doublewrite\_path](xtradb-performance-improvements-io-bound-highly-concurrent-workloads.md#innodb_parallel_doublewrite_path) variable. <br> Enabling the [innodb\_parallel\_dblwr\_encrypt](#innodb_parallel_dblwr_encrypt) controlled whether the parallel doublewrite pages were encrypted or not. In case the parallel doublewrite buffer was disabled ([innodb\_parallel\_doublewrite\_path](xtradb-performance-improvements-io-bound-highly-concurrent-workloads.md#innodb_parallel_doublewrite_path) was set to empty string),the doublewrite buffer pages were located in the system tablespace (ibdata1). The system tablespace itself could be encrypted by setting [innodb\_sys\_tablespace\_encrypt](encrypting-system-tablespace.md#innodb_sys_tablespace_encrypt), which also encrypted the doublewrite buffer pages.|
 
 For *Percona Server for MySQL* versions below *Percona Server for MySQL* version 8.0.23-14, *Percona* encrypts the `doublewrite buffer` using [innodb_parallel_dblwr_encrypt](#innodb_parallel_dblwr_encrypt).
 

docs/encryption-functions-overview.md

@@ -1,9 +1,7 @@
-## Encryption functions overview
+# Encryption functions overview
 
 This document provides comprehensive information about encryption functions that transform plaintext data into encrypted ciphertext. These functions provide robust security measures that require proper documentation to implement and maintain effectively. This guide offers the necessary information for successful implementation.
 
-
-
 ## Overview of capabilities
 
 This documentation will guide you through:
@@ -16,12 +14,8 @@ This documentation will guide you through:
 
 * Avoiding common implementation pitfalls
 
-
-
-
 First, let's review some key terms you'll encounter throughout this guide.
 
-
 ## Glossary of terms
 
 Here's a quick reference guide to the cryptographic terms used in this document:
@@ -122,7 +116,7 @@ Percona Server for MySQL 8.0.41 introduces several important new features that e
 
 ### Other new features
 
-* [`encryption_udf.legacy_padding_scheme`](#encryption_udflegacy_padding_scheme) system variable - provides compatibility with legacy systems and previous implementations
+* [`encryption_udf.legacy_padding_scheme`](encryption-functions.md#encryption_udflegacy_padding_scheme) system variable - provides compatibility with legacy systems and previous implementations
 
 * Character set awareness - ensures proper handling of different character encodings during encryption operations
 

docs/encryption-functions.md

@@ -30,56 +30,24 @@
 
 ### Function quick reference
 
-<table>
-<tr>
-<th>Category</th>
-<th>Function</th>
-<th>What It Does</th>
-<th>Common Use Case</th>
-</tr>
-<tr>
-<td rowspan="2"><strong>Encryption</strong></td>
-<td><a href="#asymmetric_encrypt">asymmetric_encrypt()</a></td>
-<td>Puts your data in a math lockbox</td>
-<td>Protecting sensitive data</td>
-</tr>
-<tr>
-<td><a href="#asymmetric_decrypt">asymmetric_decrypt()</a></td>
-<td>Opens the lockbox and gets your data back</td>
-<td>Retrieving protected data</td>
-</tr>
-<tr>
-<td rowspan="2"><strong>Key Management</strong></td>
-<td><a href="#create_asymmetric_priv_key">create_asymmetric_priv_key()</a></td>
-<td>Makes your secret key</td>
-<td>Creating your private key</td>
-</tr>
-<tr>
-<td><a href="#create_asymmetric_pub_key">create_asymmetric_pub_key()</a></td>
-<td>Creates a shareable public key</td>
-<td>Generating keys to distribute</td>
-</tr>
-<tr>
-<td rowspan="2"><strong>Digital Signatures</strong></td>
-<td><a href="#asymmetric_sign">asymmetric_sign()</a></td>
-<td>Stamps your message with your secret key</td>
-<td>Proving a message is from you</td>
-</tr>
-<tr>
-<td><a href="#asymmetric_verify">asymmetric_verify()</a></td>
-<td>Checks if a signature is real or fake</td>
-<td>Verifying message authenticity</td>
-</tr>
-</table>
+| Category | Function   | What It Does  | Common Use Case  |
+|----------|------------|---------------|-------------------|
+| **Encryption**  | [asymmetric_encrypt()](#asymmetric_encryptalgorithm-str-key_str) | Puts your data in a math lockbox             | Protecting sensitive data   |
+|                 | [asymmetric_decrypt()](#asymmetric_decryptalgorithm-crypt_str-key_str) | Opens the lockbox and gets your data back    | Retrieving protected data   |
+| **Key Management** | [create_asymmetric_priv_key()](#create_asymmetric_priv_keyalgorithm-key_len) | Makes your secret key    | Creating your private key   |
+|               | [create_asymmetric_pub_key()](#create_asymmetric_pub_keyalgorithm-priv_key_str) | Creates a shareable public key | Generating keys to distribute |
+| **Digital Signatures** | [asymmetric_sign()](#asymmetric_signalgorithm-digest_str-priv_key_str-digest_type-padding) | Stamps your message with your secret key   | Proving a message is from you |
+|                    | [asymmetric_verify()](#asymmetric_verifyalgorithm-digest_str-sig_str-pub_key_str-digest_type-padding) | Checks if a signature is real or fake  | Verifying message authenticity |
+
 
 ### Asymmetric encryption functions
 
 These functions implement public key cryptography utilizing key pairs. The encryption and decryption operations require different keys from the same key pair.
 
 | Function Name | Purpose |
 | --- | --- |
-| [asymmetric_encrypt](#asymmetric_encrypt) | Encrypts plaintext data using asymmetric cryptography. Only the corresponding key can decrypt. |
-| [asymmetric_decrypt](#asymmetric_decrypt) | Decrypts ciphertext that was encrypted with the corresponding asymmetric key. |
+| [asymmetric_encrypt](#asymmetric_encryptalgorithm-str-key_str) | Encrypts plaintext data using asymmetric cryptography. Only the corresponding key can decrypt. |
+| [asymmetric_decrypt](#asymmetric_decryptalgorithm-crypt_str-key_str) | Decrypts ciphertext that was encrypted with the corresponding asymmetric key. |
 
 
 ### Asymmetric key management functions
@@ -88,8 +56,8 @@ These functions facilitate the generation and management of asymmetric cryptogra
 
 | Function Name | Description |
 | --- | --- |
-| [create_asymmetric_priv_key](#create_asymmetric_priv_key) | Generates a private key with specified algorithm and security parameters |
-| [create_asymmetric_pub_key](#create_asymmetric_pub_key) | Derives the corresponding public key from a private key for distribution |
+| [create_asymmetric_priv_key](#create_asymmetric_priv_keyalgorithm-key_len) | Generates a private key with specified algorithm and security parameters |
+| [create_asymmetric_pub_key](#create_asymmetric_pub_keyalgorithm-priv_key_str) | Derives the corresponding public key from a private key for distribution |
 
 
 ### Digital Signature functions
@@ -98,8 +66,8 @@ These functions implement digital signature operations for message authenticatio
 
 | Function Name | Description |
 | --- | --- |
-| [asymmetric_sign](#asymmetric_sign) | Applies a cryptographic signature to a message digest using a private key |
-| [asymmetric_verify](#asymmetric_verify) | Validates the authenticity of a digital signature using the corresponding public key |
+| [asymmetric_sign](#asymmetric_signalgorithm-digest_str-priv_key_str-digest_type-padding) | Applies a cryptographic signature to a message digest using a private key |
+| [asymmetric_verify](#asymmetric_verifyalgorithm-digest_str-sig_str-pub_key_str-digest_type-padding) | Validates the authenticity of a digital signature using the corresponding public key |
 
 ### Diffie-Hellman functions
 
@@ -109,8 +77,8 @@ These functions implement digital signature operations for message authenticatio
 
 | Function Name | Description | Application |
 | --- | --- | --- |
-| [asymmetric_derive](#asymmetric_derive) | Generates a shared cryptographic secret through asymmetric key combination | When implementing secure communication channels between parties |
-| [create_dh_parameters](#create_dh_parameters) | Generates the prime numbers and parameters required for Diffie-Hellman key exchange | As a prerequisite for Diffie-Hellman key generation |
+| [asymmetric_derive](#asymmetric_derivepub_key_str-priv_key_str) | Generates a shared cryptographic secret through asymmetric key combination | When implementing secure communication channels between parties |
+| [create_dh_parameters](#create_dh_parameterskey_len) | Generates the prime numbers and parameters required for Diffie-Hellman key exchange | As a prerequisite for Diffie-Hellman key generation |
 
 
 ### Encryption threshold variables
@@ -121,43 +89,13 @@ These functions implement digital signature operations for message authenticatio
 
 Keys that are too strong might slow down your system. It's like having a super-heavy padlock that takes forever to open.
 
-<table>
-<tr>
-<th>Setting Name</th>
-<th>What It Does</th>
-<th>Default</th>
-<th>Range</th>
-<th>Performance Impact</th>
-</tr>
-<tr>
-<td><a href="#encryption_udfdh_bits_threshold">encryption_udf.dh_bits_threshold</a></td>
-<td>Sets how strong Diffie-Hellman keys can be</td>
-<td>10000</td>
-<td>1024-10000</td>
-<td>Higher values significantly increase key generation time</td>
-</tr>
-<tr>
-<td><a href="#encryption_udfdsa_bits_threshold">encryption_udf.dsa_bits_threshold</a></td>
-<td>Sets how strong DSA keys can be</td>
-<td>9984</td>
-<td>1024-9984</td>
-<td>Higher values increase key generation time</td>
-</tr>
-<tr>
-<td><a href="#encryption_udfrsa_bits_threshold">encryption_udf.rsa_bits_threshold</a></td>
-<td>Sets how strong RSA keys can be</td>
-<td>16384</td>
-<td>1024-16384</td>
-<td>Higher values increase key generation and encryption/decryption time</td>
-</tr>
-<tr>
-<td><a href="#encryption_udflegacy_padding">encryption_udf.legacy_padding</a></td>
-<td>Turns old-style padding on or off</td>
-<td>OFF</td>
-<td>ON/OFF</td>
-<td>Minor impact on encryption speed, major impact on security</td>
-</tr>
-</table>
+| Setting Name | What It Does | Default | Range  | Performance Impact |
+|--------------|--------------|---------|--------|--------------------|
+| [encryption_udf.dh_bits_threshold](#encryption_udfdh_bits_threshold) | Sets how strong Diffie-Hellman keys can be  | 10000   | 1024-10000   | Higher values significantly increase key generation time |
+| [encryption_udf.dsa_bits_threshold](#encryption_udfdsa_bits_threshold) | Sets how strong DSA keys can be  | 9984  | 1024-9984 | Higher values increase key generation time   |
+| [encryption_udf.rsa_bits_threshold](#encryption_udfrsa_bits_threshold) | Sets how strong RSA keys can be | 16384   | 1024-16384 | Higher values increase key generation and encryption/decryption time |
+| [encryption_udf.legacy_padding](#encryption_udflegacy_padding_scheme) | Turns old-style padding on or off | OFF | ON/OFF | Minor impact on encryption speed, major impact on security  |
+
 ---
 
 
@@ -193,7 +131,7 @@ SELECT * FROM mysql.component;
 ---
 
 
-## Asymmetric_decrypt(*algorithm, crypt_str, key_str*){asymmetric_decrypt}
+## Asymmetric_decrypt(*algorithm, crypt_str, key_str*)
 
 > 🔓 **Data Decryption Function**
 >
@@ -246,7 +184,7 @@ The function returns the original plaintext message decoded from the ciphertext.
 ---
 
 
-## Asymmetric_derive(*pub_key_str, priv_key_str*){asymmetric_derive}
+## Asymmetric_derive(*pub_key_str, priv_key_str*)
 
 > 🤝 **Shared secret generation**
 >
@@ -288,7 +226,7 @@ The function returns the original plaintext message decoded from the ciphertext.
 ---
 
 
-## Asymmetric_encrypt(*algorithm, str, key_str*){asymmetric_encrypt}
+## Asymmetric_encrypt(*algorithm, str, key_str*)
 
 > 🔒 **Data Encryption Function**
 >
@@ -338,10 +276,11 @@ The function returns the encrypted ciphertext as binary data.
 </details>
 
 ⚠️ **Size Limits**: Remember that your message size is limited by your key size and padding method. For a 2048-bit key with OAEP padding, your message must be smaller than (2048/8)-42 = 214 bytes.
+
 ---
 
 
-## Asymmetric_sign(*algorithm, digest_str, priv_key_str, digest_type, [padding]*){asymmetric_sign}
+## Asymmetric_sign(*algorithm, digest_str, priv_key_str, digest_type, [padding]*)
 
 > ✍️ **Digital Signature Function**
 >
@@ -413,7 +352,7 @@ The function returns a digital signature as binary data that cryptographically p
 ---
 
 
-## Asymmetric_verify(*algorithm, digest_str, sig_str, pub_key_str, digest_type, [padding]*){asymmetric_verify}
+## Asymmetric_verify(*algorithm, digest_str, sig_str, pub_key_str, digest_type, [padding]*)
 
 > 🔍 **Signature verification function**
 >
@@ -495,7 +434,7 @@ The function returns a binary verification result:
 </details>
 
 ---
-## Create_asymmetric_priv_key(*algorithm, key_len*){create_asymmetric_priv_key}
+## Create_asymmetric_priv_key(*algorithm, key_len*)
 
 > 🔑 **Private key generation function**
 >
@@ -541,7 +480,7 @@ This works for RSA and DSA keys. DH keys are quick, so no worries there.
 
 ---
 
-## Create_asymmetric_pub_key(*algorithm, priv_key_str*){create_asymmetric_pub_key}
+## Create_asymmetric_pub_key(*algorithm, priv_key_str*)
 
 > 🔓 **Public key extraction function**
 >
@@ -567,12 +506,13 @@ A public key in PEM format - another block of garbled text you can freely share.
 2. **priv_key_str** - Your secret private key
    * Must be in PEM
 
-## Create_dh_parameters(*key_len*){create_dh_parameters}
+## Create_dh_parameters(*key_len*)
 
 This function creates the special math values for Diffie-Hellman keys. It's like creating a recipe that two people will follow to create identical secret sauces without ever sharing their individual ingredients.
 
 ### Warning: Patience required!
 This can take a LONG time - much longer than making regular keys. Cancel with:
+
 ```
 KILL [QUERY|CONNECTION] <id>
 ```
@@ -590,7 +530,8 @@ A block of special values in PEM format. You'll use these later when creating DH
 * Choose between 1,024 and 10,000 bits
 * Default is 10,000 (strongest but slowest)
 * Admins can adjust the maximum with encryption_udf.dh_bits_threshold
-## Create_digest(*digest_type, str*){create_digest}
+
+## Create_digest(*digest_type, str*)
 
 Creates a digest from the given string using the given digest type. The digest string can be used with asymmetric_sign and asymmetric_verify.