fix typo 'deprecatedcapaibilities'

Signed-off-by: Daniel Ziegenberg <[email protected]>
moodle · Mar 22, 2024 · 78184b9 · 78184b9
1 parent 23c6c2f
commit 78184b9
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 4 deletions.
diff --git 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
@@ -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
@@ -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
@@ -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.