diff --git a/doc/administration/auth/ldap/index.md b/doc/administration/auth/ldap/index.md index 8c52ffd0346126d4aefaa069f8d93d5d8dc50c13..7ffb5f1447a6aef5d7787b47b884861d33155975 100644 --- a/doc/administration/auth/ldap/index.md +++ b/doc/administration/auth/ldap/index.md @@ -472,9 +472,9 @@ exchanged but no validation of the LDAP server's SSL certificate is performed. Not implemented by `Net::LDAP`. -You should disable anonymous LDAP authentication and enable simple or SASL -authentication. The TLS client authentication setting in your LDAP server cannot -be mandatory and clients cannot be authenticated with the TLS protocol. +You should disable anonymous LDAP authentication and enable simple or Simple Authentication +and Security Layer (SASL) authentication. The TLS client authentication setting in your LDAP server +cannot be mandatory and clients cannot be authenticated with the TLS protocol. ## Multiple LDAP servers **(PREMIUM SELF)** diff --git a/doc/administration/instance_limits.md b/doc/administration/instance_limits.md index 682fba804a695b25a340c611f1ed1b27883d1408..bb9fe9be7f481c56ed8907257a4a229dc87afbc9 100644 --- a/doc/administration/instance_limits.md +++ b/doc/administration/instance_limits.md @@ -226,7 +226,7 @@ Activity history for projects and individuals' profiles was limited to one year > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/14939) in GitLab 12.7. -There is a limit when embedding metrics in GFM for performance reasons. +There is a limit when embedding metrics in GitLab Flavored Markdown (GFM) for performance reasons. - **Max limit**: 100 embeds. diff --git a/doc/raketasks/backup_restore.md b/doc/raketasks/backup_restore.md index b6f772dee17510f5b8c629b56f227d50e19d232e..21766a0726ab438b5b2331faca78a9653264a0c7 100644 --- a/doc/raketasks/backup_restore.md +++ b/doc/raketasks/backup_restore.md @@ -1129,14 +1129,14 @@ GitLab backup script to be too slow. If your GitLab instance has a lot of forked projects, the regular backup task also duplicates the Git data for all of them. In these cases, consider using file system snapshots as part of your backup strategy. -Example: Amazon EBS +Example: Amazon Elastic Block Store (EBS) > A GitLab server using Omnibus GitLab hosted on Amazon AWS. > An EBS drive containing an ext4 file system is mounted at `/var/opt/gitlab`. > In this case you could make an application backup by taking an EBS snapshot. > The backup includes all repositories, uploads and PostgreSQL data. -Example: LVM snapshots + rsync +Example: Logical Volume Manager (LVM) snapshots + rsync > A GitLab server using Omnibus GitLab, with an LVM logical volume mounted at `/var/opt/gitlab`. > Replicating the `/var/opt/gitlab` directory using rsync would not be reliable because too many files would change while rsync is running. diff --git a/doc/security/webhooks.md b/doc/security/webhooks.md index c0e5d0695cc4804093abfc2738af836273fdb103..7c94ad0bed24d8191cc8895901b6e0a52ea2b586 100644 --- a/doc/security/webhooks.md +++ b/doc/security/webhooks.md @@ -74,7 +74,7 @@ allowlist: The allowed entries can be separated by semicolons, commas or whitespaces (including newlines) and be in different formats like hostnames, IP addresses and/or IP ranges. IPv6 is supported. Hostnames that contain Unicode characters should -use IDNA encoding. +use Internationalising Domain Names in Applications (IDNA) encoding. The allowlist can hold a maximum of 1000 entries. Each entry can be a maximum of 255 characters.