Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix typo 'deprecatedcapaibilities' #929

Merged
merged 1 commit into from
Mar 22, 2024
+4 −4
Merged

fix typo 'deprecatedcapaibilities' #929

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/apis/subsystems/access.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-4.1/apis/subsystems/access.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-4.2/apis/subsystems/access.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-4.3/apis/subsystems/access.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
Loading