Replace emphasis and blockquote HTML code

Replaced them with the proper markdown alternatives.

Author: dingo-d

wordpress-coding-standards/php.md

@@ -21,7 +21,7 @@ Text that goes into attributes should be run through `esc_attr()` so that single
 
 ### Indentation
 
-Your indentation should always reflect logical structure. Use <strong>real tabs</strong> and <strong>not spaces</strong>, as this allows the most flexibility across clients.
+Your indentation should always reflect logical structure. Use **real tabs** and **not spaces**, as this allows the most flexibility across clients.
 
 Exception: if you have a block of code that would be more readable if things are aligned, use spaces:
 
@@ -32,7 +32,7 @@ Exception: if you have a block of code that would be more readable if things are
 [tab]$foo5  = 'somevalue4';
 ```
 
-For associative arrays, <em>each item</em> should start on a new line when the array contains more than one item:
+For associative arrays, _each item_ should start on a new line when the array contains more than one item:
 
 ```php
 $query = new WP_Query( array( 'ID' => 123 ) );
@@ -72,7 +72,7 @@ switch ( $type ) {
 }
 ```
 
-<strong>Rule of thumb:</strong> Tabs should be used at the beginning of the line for indentation, while spaces can be used mid-line for alignment.
+**Rule of thumb:** Tabs should be used at the beginning of the line for indentation, while spaces can be used mid-line for alignment.
 
 ### Brace Style
 
@@ -111,7 +111,7 @@ foreach ( $items as $item ) {
 }
 ```
 
-Note that requiring the use of braces just means that <em>single-statement inline control structures</em> are prohibited. You are free to use the [alternative syntax for control structures](https://www.php.net/manual/en/control-structures.alternative-syntax.php) (e.g. `if`/`endif`, `while`/`endwhile`)—especially in your templates where PHP code is embedded within HTML, for instance:
+Note that requiring the use of braces just means that _single-statement inline control structures_ are prohibited. You are free to use the [alternative syntax for control structures](https://www.php.net/manual/en/control-structures.alternative-syntax.php) (e.g. `if`/`endif`, `while`/`endwhile`)—especially in your templates where PHP code is embedded within HTML, for instance:
 
 ```php
 <?php if ( have_posts() ) : ?>
@@ -219,7 +219,7 @@ if ( $a === $b ) { ?>
 
 ### No Shorthand PHP Tags
 
-<strong>Important:</strong> Never use shorthand PHP start tags. Always use full PHP tags.
+**Important:** Never use shorthand PHP start tags. Always use full PHP tags.
 
 Correct:
 
@@ -568,23 +568,24 @@ switch ( $foo ) {
 
 The `goto` statement must never be used.
 
-The `eval()` construct is <em>very dangerous</em>, and is impossible to secure. Additionally, the `create_function()` function, which internally performs an `eval()`, is deprecated in PHP 7.2. Both of these must not be used.
+The `eval()` construct is _very dangerous_, and is impossible to secure. Additionally, the `create_function()` function, which internally performs an `eval()`, is deprecated in PHP 7.2. Both of these must not be used.
 
 ### Error Control Operator `@`
 
 As noted in the [PHP docs](https://www.php.net/manual/en/language.operators.errorcontrol.php):
 
-<blockquote>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.</blockquote>
+> 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.
 
 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:
 
-<blockquote>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.</blockquote>
+> 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.
 
 ### Don't `extract()`
 
 Per [#22400](https://core.trac.wordpress.org/ticket/22400 "Remove all, or at least most, uses of extract() within WordPress"):
-<blockquote>`extract()` is a terrible function that makes code harder to debug and harder to understand. We should discourage it's [sic] use and remove all of our uses of it.
-</blockquote>
+
+> `extract()` is a terrible function that makes code harder to debug and harder to understand. We should discourage it's [sic] use and remove all of our uses of it.
+
 
 Joseph Scott has [a good write-up of why it's bad](https://blog.josephscott.org/2009/02/05/i-dont-like-phps-extract-function/).