Deployed b1b3563 with MkDocs version: 1.4.2

troubleshooting/index.html

@@ -1207,7 +1207,7 @@ <h2 id="ask-for-help">Ask for help</h2>
 <p>If Workbench "isn't working the way you expect", the documentation is likely unclear. Crashes are usually caused by sloppy Python coding. Reporting either is a great way to contribute to Islandora Workbench.</p>
 <h2 id="but-before-you-ask">But before you ask...</h2>
 <p>The first step you should take while troubleshooting a Workbench failure is to use Islandora's graphical user interface to create/edit/delete a node/media/taxonomy term. If Islandora works without error, you have confirmed that the problem you are experiencing is likely isolated to Workbench and is not being caused by an underlying problem with Islandora.</p>
-<p>Next, if you have eliminated Islandora as the cause of the problem you are experiencing, you might be able to fix the problem by pulling in the most recent Workbench code. The best way to keep it up to date is to pull in the latest commits from the Github repository periodically, but if you haven't done that in a while, within the "islandora_workbench" directory, run the following git commands:</p>
+<p>Next, if you have eliminated Islandora as the cause of the Workbench problem you are experiencing, you might be able to fix the problem by pulling in the most recent Workbench code. The best way to keep it up to date is to pull in the latest commits from the Github repository periodically, but if you haven't done that in a while, within the "islandora_workbench" directory, run the following git commands:</p>
 <ol>
 <li><code>git branch</code>, which should tell whether you're currently in the "main" branch. If you are:</li>
 <li><code>git pull</code>, which will fetch the most recent code and and merge it into the code you are running.</li>