Final minor grammar changes

Co-authored-by: Juliette <[email protected]>

Author: dingo-d

wordpress-coding-standards/php.md

@@ -6,7 +6,7 @@ While not all code may fully comply with these standards (yet), all newly commit
 
 Keep the following rules in mind when writing PHP code for WordPress, whether for core programming code, plugins, or themes.
 
-See also: [PHP Inline Documentation Standards](https://developer.wordpress.org/coding-standards/inline-documentation-standards/php/).
+Also see [PHP Inline Documentation Standards](https://developer.wordpress.org/coding-standards/inline-documentation-standards/php/) for further guidelines.
 
 ## Single and Double Quotes
 
@@ -133,7 +133,7 @@ Note that requiring the use of braces means that _single-statement inline contro
 
 Using long array syntax ( `array( 1, 2, 3 )` ) for declaring arrays is generally more readable than short array syntax ( `[ 1, 2, 3 ]` ), particularly for those with vision difficulties. Additionally, it's much more descriptive for beginners.
 
-Arrays must be declared using the long array syntax.
+Arrays must be declared using long array syntax.
 
 ## Closures (Anonymous Functions)
 
@@ -237,11 +237,11 @@ Incorrect:
 
 ## Remove Trailing Spaces
 
-Remove trailing whitespace at the end of each line. Omitting the closing PHP tag at the end of a file is preferred. If you use the tag, make sure you remove the trailing whitespace.
+Remove trailing whitespace at the end of each line. Omitting the closing PHP tag at the end of a file is preferred. If you use the tag, make sure you remove trailing whitespace.
 
 ## Space Usage
 
-Always put spaces after commas, and on both sides of the logical, comparison, string, and assignment operators.
+Always put spaces after commas, and on both sides of logical, comparison, string and assignment operators.
 
 ```php
 x === 23
@@ -279,7 +279,7 @@ When performing logical comparisons, do it like so:
 if ( ! $foo ) { ...
 ```
 
-[Type casts](https://www.php.net/manual/en/language.types.type-juggling.php#language.types.typecasting) must be lowercase. Always prefer the short form of type casts, `(int)` instead of `(integer)` and `(bool)` rather than `(boolean)`. For float casts use `(float)`, not `(real)` which is [deprecated](https://wiki.php.net/rfc/deprecations_php_7_4#the_real_type) in PHP 7.4, and removed in PHP 8:
+[Type casts](https://www.php.net/manual/en/language.types.type-juggling.php#language.types.typecasting) must be lowercase. Always prefer the short form of type casts, `(int)` instead of `(integer)` and `(bool)` rather than `(boolean)`. For float casts use `(float)`, not `(real)` which is [deprecated](https://www.php.net/manual/en/migration74.deprecated.php#migration74.deprecated.core.real) in PHP 7.4, and removed in PHP 8:
 
 ```php
 foreach ( (array) $foo as $bar ) { ...
@@ -348,7 +348,7 @@ See [Data Validation](https://developer.wordpress.org/plugins/security/data-vali
 
 Avoid touching the database directly. If there is a defined function that can get the data you need, use it. Database abstraction (using functions instead of queries) helps keep your code forward-compatible and, in cases where results are cached in memory, it can be many times faster.
 
-If you must touch the database, consider discussing it in Slack and creating a [Trac](https://core.trac.wordpress.org/) ticket.
+If you must touch the database, consider creating a [Trac](https://core.trac.wordpress.org/) ticket. There you can discuss the possibility of adding a new function to cover the functionality you wanted, for the next WordPress version. 
 
 ## Naming Conventions
 
@@ -457,7 +457,7 @@ Dynamic hooks should be named using interpolation rather than concatenation for
 
 Dynamic hooks are hooks that include dynamic values in their tag name, e.g. `{$new_status}_{$post->post_type}` (publish_post).
 
-Variables used in hook tags should be wrapped in curly braces `{` and `}`, with the complete outer tag name wrapped in double-quotes. This is to ensure PHP can correctly parse the given variables' types within the interpolated string.
+Variables used in hook tags should be wrapped in curly braces `{` and `}`, with the complete outer tag name wrapped in double quotes. This is to ensure PHP can correctly parse the given variables' types within the interpolated string.
 
 ```php
 do_action( "{$new_status}_{$post->post_type}", $post->ID, $post );
@@ -575,11 +575,11 @@ The `eval()` construct is _very dangerous_ and is impossible to secure. Addition
 
 As noted in the [PHP docs](https://www.php.net/manual/en/language.operators.errorcontrol.php):
 
-> PHP supports one error control operator: the at sign (`@`). When prepended to an expression in PHP, any error messages that might be generated by that expression will be ignored.
+> PHP supports one error control operator: the at sign (@). When prepended to an expression in PHP, any diagnostic error that might be generated by that expression will be suppressed.
 
 While this operator does exist in Core, it is often used lazily instead of doing proper error checking. Its use is highly discouraged, as even the PHP docs also state:
 
-> Warning: Currently the "@" error-control operator prefix will even disable error reporting for critical errors that will terminate script execution. Among other things, this means that if you use "@" to suppress errors from a certain function and either it isn't available or has been mistyped, the script will die right there with no indication as to why.
+> Warning: Prior to PHP 8.0.0, it was possible for the @ operator to disable critical errors that will terminate script execution. For example, prepending @ to a call of a function that did not exist, by being unavailable or mistyped, would cause the script to terminate with no indication as to why.
 
 ## Don't `extract()`