XSD: minor touch up

Author: jrfnl

PHPCSDebug/Docs/Debug/TokenListStandard.xml

@@ -1,4 +1,8 @@
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd" title="Token List">
+<?xml version="1.0"?>
+<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
+    title="Token List"
+    >
     <standard>
     <![CDATA[
     Lists how PHPCS tokenizes code.

README.md

@@ -184,17 +184,17 @@ In order to use it, you'll need to add the schema related attributes to the `doc
 
 ```xml
 <documentation
-    title="Name of the sniff"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
+    title="Name of the sniff"
 >
 ```
 
 If your IDE or editor supports automatic validation of XML files, you will be notified if your documentation XML file has the correct number of elements, correct type and number of certain attributes, and title length among other things.
 
 #### Validating your docs against the XSD
 
-You can validate your PHPCS XML documentation against the XSD file using [xmllint](https://gnome.pages.gitlab.gnome.org/libxml2/xmllint.html). This validation can be run locally if you have xmllint installed, as well as in CI (continuous integration).
+You can validate your PHPCS XML documentation against the XSD file using [xmllint](http://xmlsoft.org/xmllint.html). This validation can be run locally if you have xmllint installed, as well as in CI (continuous integration).
 
 An example of a workflow job for GitHub Actions CI looks like this:
 
@@ -217,7 +217,7 @@ jobs:
         run: xmllint --noout --schema vendor/phpcsstandards/phpcsdevtools/DocsXsd/phpcsdocs.xsd ./YourRuleset/Docs/**/*Standard.xml
 ```
 
-You'd need to replace the `YourRuleset` with the name of your ruleset of course.
+:point_right: You'll need to replace the `YourRuleset` within the command with the name of your ruleset (of course).
 
 Contributing
 -------