From cf26ab0ea9c0321963696412d6316946ccc644ee Mon Sep 17 00:00:00 2001
From: Brown <github@muglug.com>
Date: Mon, 27 Apr 2020 23:11:05 -0400
Subject: [PATCH] Use html entities

---
 docs/running_psalm/configuration.md | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/docs/running_psalm/configuration.md b/docs/running_psalm/configuration.md
index 4b69d6122..11147bbca 100644
--- a/docs/running_psalm/configuration.md
+++ b/docs/running_psalm/configuration.md
@@ -341,8 +341,8 @@ Allows you to hard-code a serializer for Psalm to use when caching data. By defa
 
 ## Project settings
 
-#### `<projectFiles>`
-Contains a list of all the directories that Psalm should inspect. You can also specify a set of files and folders to ignore with the `<ignoreFiles>` directive, e.g.
+#### &lt;projectFiles>`
+Contains a list of all the directories that Psalm should inspect. You can also specify a set of files and folders to ignore with the &lt;ignoreFiles>` directive, e.g.
 ```xml
 <projectFiles>
   <directory name="src" />
@@ -352,22 +352,22 @@ Contains a list of all the directories that Psalm should inspect. You can also s
 </projectFiles>
 ```
 
-#### `<fileExtensions>`
+#### &lt;fileExtensions&gt;
 Optional.  A list of extensions to search over. See [Checking non-PHP files](checking_non_php_files.md) to understand how to extend this.
 
-#### `<plugins>`
+#### &lt;plugins&gt;
 Optional.  A list of `<plugin filename="path_to_plugin.php" />` entries. See the [Plugins](plugins/using_plugins.md) section for more information.
 
-#### `<issueHandlers>`
+#### &lt;issueHandlers&gt;
 Optional.  If you don't want Psalm to complain about every single issue it finds, the issueHandler tag allows you to configure that. [Dealing with code issues](dealing_with_code_issues.md) tells you more.
 
-#### `<mockClasses>`
+#### &lt;mockClasses&gt;
 Optional. Do you use mock classes in your tests? If you want Psalm to ignore them when checking files, include a fully-qualified path to the class with `<class name="Your\Namespace\ClassName" />`
 
-#### `<stubs>`
-Optional. If your codebase uses classes and functions that are not visible to Psalm via reflection (e.g. if there are internal packages that your codebase relies on that are not available on the machine running Psalm), you can use stub files. Used by PhpStorm (a popular IDE) and others, stubs provide a description of classes and functions without the implementations. You can find a list of stubs for common classes [here](https://github.com/JetBrains/phpstorm-stubs). List out each file with `<file name="path/to/file.php" />`.
+#### &lt;stubs&gt;
+Optional. If your codebase uses classes and functions that are not visible to Psalm via reflection (e.g. if there are internal packages that your codebase relies on that are not available on the machine running Psalm), you can use stub files. Used by PhpStorm (a popular IDE) and others, stubs provide a description of classes and functions without the implementations. You can find a list of stubs for common classes [here](https://github.com/JetBrains/phpstorm-stubs). List out each file with `file name="path/to/file.php" />`.
 
-#### `<ignoreExceptions>`
+#### &lt;ignoreExceptions&gt;
 Optional.  A list of exceptions to not report for `checkForThrowsDocblock` or `checkForThrowsInGlobalScope`. If an exception has `onlyGlobalScope` set to `true`, only `checkForThrowsInGlobalScope` is ignored for that exception, e.g.
 ```xml
 <ignoreExceptions>
@@ -375,7 +375,7 @@ Optional.  A list of exceptions to not report for `checkForThrowsDocblock` or `c
 </ignoreExceptions>
 ```
 
-#### `<globals>`
+#### &lt;globals&gt;
 Optional.  If your codebase uses global variables that are accessed with the `global` keyword, you can declare their type.  e.g.
 ```xml
 <globals>