From 78184b9edfff1ad5c273145f0a36b45acf313055 Mon Sep 17 00:00:00 2001 From: Daniel Ziegenberg Date: Fri, 22 Mar 2024 14:06:09 +0100 Subject: [PATCH] fix typo 'deprecatedcapaibilities' Signed-off-by: Daniel Ziegenberg --- docs/apis/subsystems/access.md | 2 +- versioned_docs/version-4.1/apis/subsystems/access.md | 2 +- versioned_docs/version-4.2/apis/subsystems/access.md | 2 +- versioned_docs/version-4.3/apis/subsystems/access.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/apis/subsystems/access.md b/docs/apis/subsystems/access.md index 0e963f0716..ffeff9c6de 100644 --- a/docs/apis/subsystems/access.md +++ b/docs/apis/subsystems/access.md @@ -84,7 +84,7 @@ To mark a capability as deprecated, edit the access.php containing the capabilit Entries in `$deprecatedcapabilities` can have a `replacement` key indicating a new or existing capability that replaces the deprecated one. If this is specified, any checks to the deprecated capability will check the replacement capability instead. A debugging message will always be output at `DEBUG_DEVELOPER` level if a deprecated capability is checked. -`$deprecatedcapaibilities` can also define an optional `message` explaining the deprecation. +`$deprecatedcapabilities` can also define an optional `message` explaining the deprecation. The following example demonstrates an access.php file where a capability has been deprecated and replaced with another. diff --git a/versioned_docs/version-4.1/apis/subsystems/access.md b/versioned_docs/version-4.1/apis/subsystems/access.md index 0e963f0716..ffeff9c6de 100644 --- a/versioned_docs/version-4.1/apis/subsystems/access.md +++ b/versioned_docs/version-4.1/apis/subsystems/access.md @@ -84,7 +84,7 @@ To mark a capability as deprecated, edit the access.php containing the capabilit Entries in `$deprecatedcapabilities` can have a `replacement` key indicating a new or existing capability that replaces the deprecated one. If this is specified, any checks to the deprecated capability will check the replacement capability instead. A debugging message will always be output at `DEBUG_DEVELOPER` level if a deprecated capability is checked. -`$deprecatedcapaibilities` can also define an optional `message` explaining the deprecation. +`$deprecatedcapabilities` can also define an optional `message` explaining the deprecation. The following example demonstrates an access.php file where a capability has been deprecated and replaced with another. diff --git a/versioned_docs/version-4.2/apis/subsystems/access.md b/versioned_docs/version-4.2/apis/subsystems/access.md index 0e963f0716..ffeff9c6de 100644 --- a/versioned_docs/version-4.2/apis/subsystems/access.md +++ b/versioned_docs/version-4.2/apis/subsystems/access.md @@ -84,7 +84,7 @@ To mark a capability as deprecated, edit the access.php containing the capabilit Entries in `$deprecatedcapabilities` can have a `replacement` key indicating a new or existing capability that replaces the deprecated one. If this is specified, any checks to the deprecated capability will check the replacement capability instead. A debugging message will always be output at `DEBUG_DEVELOPER` level if a deprecated capability is checked. -`$deprecatedcapaibilities` can also define an optional `message` explaining the deprecation. +`$deprecatedcapabilities` can also define an optional `message` explaining the deprecation. The following example demonstrates an access.php file where a capability has been deprecated and replaced with another. diff --git a/versioned_docs/version-4.3/apis/subsystems/access.md b/versioned_docs/version-4.3/apis/subsystems/access.md index 0e963f0716..ffeff9c6de 100644 --- a/versioned_docs/version-4.3/apis/subsystems/access.md +++ b/versioned_docs/version-4.3/apis/subsystems/access.md @@ -84,7 +84,7 @@ To mark a capability as deprecated, edit the access.php containing the capabilit Entries in `$deprecatedcapabilities` can have a `replacement` key indicating a new or existing capability that replaces the deprecated one. If this is specified, any checks to the deprecated capability will check the replacement capability instead. A debugging message will always be output at `DEBUG_DEVELOPER` level if a deprecated capability is checked. -`$deprecatedcapaibilities` can also define an optional `message` explaining the deprecation. +`$deprecatedcapabilities` can also define an optional `message` explaining the deprecation. The following example demonstrates an access.php file where a capability has been deprecated and replaced with another.