Fix the variable name (8.0) (#541)

alina-derkach-oaza · web-flow · commit 12e6fad3083e · 2025-07-07T17:04:50.000+02:00
Update audit-log-filter-variables.md
diff --git a/docs/audit-log-filter-variables.md b/docs/audit-log-filter-variables.md
@@ -613,7 +613,7 @@ The default value is 0 (zero). This value disables the expiration of passwords.
 
 If the plugin starts and encryption is enabled, the plugin checks for an audit log filter encryption password. If a password is not found, the plugin generates a random password.
 
-Call `audit_log_filter_encryption_set() to set a specific password.
+Call [audit_log_encryption_password_set(new_password)](#audit_log_encryption_password_setnew_password) to set a specific password.
 
 
 ### `audit_log_filter_prune_seconds`
@@ -710,7 +710,7 @@ Defines the Audit Log filter plugin's logging method. The valid values are the f
 | Data type | String  |
 | Default | LOG_USER |
 
-Specifies the syslog `facility` value. The option has the same meaning as the appropriate parameter described in the [syslog(3) manual](https://linux.die.net/man/3/syslog).
+Specifies the syslog `facility` value. The option has the same meaning as the appropriate parameter described in the [syslog(3) manual](https://man7.org/linux/man-pages/man3/syslog.3.html).
 
 
 ### `audit_log_filter_syslog_priority`
@@ -723,7 +723,7 @@ Specifies the syslog `facility` value. The option has the same meaning as the ap
 | Data type | String  |
 | Default | LOG_INFO |
 
-Defines the `priority` value for the syslog. The option has the same meaning as the appropriate parameter described in the [syslog(3) manual](https://linux.die.net/man/3/syslog).
+Defines the `priority` value for the syslog. The option has the same meaning as the appropriate parameter described in the [syslog(3) manual](https://man7.org/linux/man-pages/man3/syslog.3.html).
 
 
 
diff --git a/docs/audit-log-plugin.md b/docs/audit-log-plugin.md
@@ -283,7 +283,7 @@ The audit Log plugin generates a log of following events.
 
 ## Stream the audit log to syslog
 
-To stream the audit log to syslog you’ll need to set audit_log_handler variable to `SYSLOG`. To control the syslog file handler, the following variables can be used: audit_log_syslog_ident, audit_log_syslog_facility, and audit_log_syslog_priority These variables have the same meaning as appropriate parameters described in the [syslog(3) manual](https://linux.die.net/man/3/syslog).
+To stream the audit log to syslog you’ll need to set audit_log_handler variable to `SYSLOG`. To control the syslog file handler, the following variables can be used: audit_log_syslog_ident, audit_log_syslog_facility, and audit_log_syslog_priority These variables have the same meaning as appropriate parameters described in the [syslog(3) manual](https://man7.org/linux/man-pages/man3/syslog.3.html).
 
 !!! note
 
@@ -879,7 +879,7 @@ will be written to syslog.
 
 This variable is used to specify the `ident` value for syslog. This variable
 has the same meaning as the appropriate parameter described in the [syslog(3)
-manual](http://linux.die.net/man/3/syslog).
+manual](https://man7.org/linux/man-pages/man3/syslog.3.html).
 
 ### `audit_log_syslog_facility`
 
@@ -893,7 +893,7 @@ manual](http://linux.die.net/man/3/syslog).
 
 This variable is used to specify the `facility` value for syslog. This
 variable has the same meaning as the appropriate parameter described in the
-[syslog(3) manual](https://linux.die.net/man/3/syslog).
+[syslog(3) manual](https://man7.org/linux/man-pages/man3/syslog.3.html).
 
 ### `audit_log_syslog_priority`
 
@@ -907,7 +907,7 @@ variable has the same meaning as the appropriate parameter described in the
 
 This variable is used to specify the `priority` value for syslog. This
 variable has the same meaning as the appropriate parameter described in the
-[syslog(3) manual](https://linux.die.net/man/3/syslog).
+[syslog(3) manual](https://man7.org/linux/man-pages/man3/syslog.3.html).
 
 ## Status Variables
 
diff --git a/docs/release-notes/Percona-Server-8.0.26-17.md b/docs/release-notes/Percona-Server-8.0.26-17.md
@@ -24,7 +24,7 @@ increased visibility. [Commercial support contracts are available](https://www.p
 
 Percona integrates a ZenFS RocksDB plugin to Percona Server for MySQL. This
 plugin places files on a raw zoned block device (ZBD) using the MyRocks File
-System interface. Percona provides a binary release for [Debian 11.1](https://www.debian.org/releases/bullseye/debian-installer/index). [Other Linux distributions](https://zonedstorage.io/docs/distributions/overview) are adding support for ZenFS, but Percona does not offer installation packages for those distributions yet. The `libzbd` package is now linked statically to the RocksDB storage engine.
+System interface. Percona provides a binary release for Debian 11.1. [Other Linux distributions](https://zonedstorage.io/docs/distributions/overview) are adding support for ZenFS, but Percona does not offer installation packages for those distributions yet. The `libzbd` package is now linked statically to the RocksDB storage engine.
 
 The following dependency libraries are updated to newer versions:
 
diff --git a/docs/start-transaction-with-consistent-snapshot.md b/docs/start-transaction-with-consistent-snapshot.md
@@ -1,6 +1,6 @@
 # Start transaction with consistent snapshot
 
-*Percona Server for MySQL* has ported *MariaDB* [enhancement](https://mariadb.com/kb/en/enhancements-for-start-transaction-with-consistent/) for `START TRANSACTION WITH CONSISTENT SNAPSHOTS` feature to *MySQL* 5.6 group commit implementation. This enhancement makes binary log positions consistent with *InnoDB* transaction snapshots.
+*Percona Server for MySQL* has ported *MariaDB* [enhancement](https://mariadb.com/docs/server/ha-and-performance/standard-replication/enhancements-for-start-transaction-with-consistent-snapshot/) for `START TRANSACTION WITH CONSISTENT SNAPSHOTS` feature to *MySQL* 5.6 group commit implementation. This enhancement makes binary log positions consistent with *InnoDB* transaction snapshots.
 
 This feature is quite useful to obtain logical backups with correct positions without running a `FLUSH TABLES WITH READ LOCK`. Binary log position can be obtained by two newly implemented status variables: [Binlog_snapshot_file](#binlog_snapshot_file) and [Binlog_snapshot_position](#binlog_snapshot_position). After starting a transaction using the `START TRANSACTION WITH CONSISTENT SNAPSHOT`, these two variables will provide you with the binlog position corresponding to the state of the database of the consistent snapshot so taken, irrespectively of which other transactions have been committed since the snapshot was taken.
 
@@ -65,4 +65,4 @@ These status variables are only available when the binary log is enabled globall
 
 ## Other reading
 
-* [MariaDB Enhancements for START TRANSACTION WITH CONSISTENT SNAPSHOT](https://mariadb.com/kb/en/enhancements-for-start-transaction-with-consistent/)
+* [MariaDB Enhancements for START TRANSACTION WITH CONSISTENT SNAPSHOT](https://mariadb.com/docs/server/ha-and-performance/standard-replication/enhancements-for-start-transaction-with-consistent-snapshot/)
diff --git a/docs/telemetry.md b/docs/telemetry.md
@@ -391,5 +391,3 @@ percona_telemetry_disable=1
 
 Restart the server after editing the configuration file. This setting ensures that the telemetry remains disabled even after a server restart.
 
-[Percona Privacy statement]: https://www.percona.com/privacy-policy#h.e34c40q8sb1a
-[disable telemetry]: #disable-telemetry

Original file line number	Diff line number	Diff line change
`@@ -391,5 +391,3 @@ percona_telemetry_disable=1`
`391`	`391`
`392`	`392`	`Restart the server after editing the configuration file. This setting ensures that the telemetry remains disabled even after a server restart.`
`393`	`393`
`394`		`-[Percona Privacy statement]: https://www.percona.com/privacy-policy#h.e34c40q8sb1a`
`395`		`-[disable telemetry]: #disable-telemetry`