word wrap docs at 120 columns.

Author: lovettchris

.vscode/settings.json

@@ -0,0 +1,4 @@
+{
+    "editor.wordWrapColumn": 120,
+    "rewrap.wrappingColumn": 120
+}

docs/dev/design.md

@@ -2,99 +2,91 @@
 
 By [Chris Lovett](http://lovettsoftware.com/), Microsoft
 
-In the GitHub repo, you'll find the core `XmlNotepad` DLL project, an `Application` project that
-builds XmlNotepad.exe, and some setup projects like `XmlNotepadSetup` which builds the .msi
-installer, and the `UnitTests` project for testing XML Notepad.
+In the GitHub repo, you'll find the core `XmlNotepad` DLL project, an `Application` project that builds XmlNotepad.exe,
+and some setup projects like `XmlNotepadSetup` which builds the .msi installer, and the `UnitTests` project for testing
+XML Notepad.
 
-The following DGML diagram shows the relationships between the main UI classes. The main form
-contains all the UI elements from the TaskList to the main XmlTreeView with Resizers in between;
-it's the launching point for the dialogs such as FormSearch, FormSchemas, FormOption, and FormAbout.
+The following DGML diagram shows the relationships between the main UI classes. The main form contains all the UI
+elements from the TaskList to the main XmlTreeView with Resizers in between; it's the launching point for the dialogs
+such as FormSearch, FormSchemas, FormOption, and FormAbout.
 
 ![ui](../assets/images/ui.png)
 
-The main tab control contains the XmlTreeView and the XsltViewer for showing XSL output. The
-XmlTreeView contains a TreeView on the left and a NodeTextView on the right and coordinates
-scrolling between these two views. Both the TreeView and NodeTextView provide the same IntelliSense
-editing functionality using a TextEditorOverlay component. The XmlTreeView implements IFindTarget,
-which is used by the Find dialog (FormSearch) to implement find/replace functionality.
+The main tab control contains the XmlTreeView and the XsltViewer for showing XSL output. The XmlTreeView contains a
+TreeView on the left and a NodeTextView on the right and coordinates scrolling between these two views. Both the
+TreeView and NodeTextView provide the same IntelliSense editing functionality using a TextEditorOverlay component. The
+XmlTreeView implements IFindTarget, which is used by the Find dialog (FormSearch) to implement find/replace
+functionality.
 
 ![find](../assets/images/ifindtarget.png)
 
 The Find dialog supports full text, regex, or XPath expressions and can filter by names or values.
 
 ## Model
 
-The core data model behind the UI is `System.Xml.XmlDocument` and its `XmlNode` objects. These
-nodes are wrapped by `TreeNode` UI objects. To facilitate support for the XML Include spec, there is a
-custom reader that processes XML Includes, and there is also a custom DomLoader that keeps track of
-line information for error messages.
+The core data model behind the UI is `System.Xml.XmlDocument` and its `XmlNode` objects. These nodes are wrapped by
+`TreeNode` UI objects. To facilitate support for the XML Include spec, there is a custom reader that processes XML
+Includes, and there is also a custom DomLoader that keeps track of line information for error messages.
 
 ![model](../assets/images/model.png)
 
 ## Validation, IntelliSense, and Custom Editors
 
-The biggest new feature is IntelliSense, which is driven by XML Schema information provided via the
-SchemaCache. For example, if your element or attribute is defined by an XSD simpleType and this
-simpleType contains a list of enumeration facets, then you will get a drop-down like this:
+The biggest new feature is IntelliSense, which is driven by XML Schema information provided via the SchemaCache. For
+example, if your element or attribute is defined by an XSD simpleType and this simpleType contains a list of enumeration
+facets, then you will get a drop-down like this:
 
 ![intellisense](../assets/images/intellisense.png)
 
-The way this works is that the Checker runs after each edit operation to validate the document and
-report errors in the TaskList. This process also puts `System.Xml.Schema.XmlSchemaType` information
-on each element and attribute in the XmlDocument; then, when editing the value of that node, the
-TextEditorOverlay uses the `XmlIntelliSenseProvider` to get back a list of possible values. In the
-above example, it returns the values from the simpleType enumeration facets. For element name
-IntelliSense in the tree view, the `XmlIntelliSenseProvider` invokes the Checker again, captures
-GetExpectedParticles and GetExpectedAttributes on the `System.Xml.Schema.XmlSchemaValidator`, and
-uses that to provide IntelliSense.
+The way this works is that the Checker runs after each edit operation to validate the document and report errors in the
+TaskList. This process also puts `System.Xml.Schema.XmlSchemaType` information on each element and attribute in the
+XmlDocument; then, when editing the value of that node, the TextEditorOverlay uses the `XmlIntelliSenseProvider` to get
+back a list of possible values. In the above example, it returns the values from the simpleType enumeration facets. For
+element name IntelliSense in the tree view, the `XmlIntelliSenseProvider` invokes the Checker again, captures
+GetExpectedParticles and GetExpectedAttributes on the `System.Xml.Schema.XmlSchemaValidator`, and uses that to provide
+IntelliSense.
 
 ![plugins](../assets/images/plugins.png)
 
-The `TextEditorOverlay` also supports custom editors like the `DateTimeEditor` or the `UriBuilder`
-or `ColorBuilder`. There are two types of custom editors: IXmlEditors, which are inline editors that
-replace the default TextBox, and IXmlBuilders, which are popup dialogs like the OpenFileDialog or
-ColorDialog. The type of editor is derived from the schema type information — "xs:date", "xs:time",
-"xs:datetime" results in the DateTimeEditor, and "xs:anyURI" results in the UriBuilder. You can also
-annotate the schema with a custom "vs:builder" attribute in the
-`http://schemas.microsoft.com/Visual-Studio-IntelliSense` namespace. See the Help content for more
-information.
+The `TextEditorOverlay` also supports custom editors like the `DateTimeEditor` or the `UriBuilder` or `ColorBuilder`.
+There are two types of custom editors: IXmlEditors, which are inline editors that replace the default TextBox, and
+IXmlBuilders, which are popup dialogs like the OpenFileDialog or ColorDialog. The type of editor is derived from the
+schema type information — "xs:date", "xs:time", "xs:datetime" results in the DateTimeEditor, and "xs:anyURI" results in
+the UriBuilder. You can also annotate the schema with a custom "vs:builder" attribute in the
+`http://schemas.microsoft.com/Visual-Studio-IntelliSense` namespace. See the Help content for more information.
 
 ## Infinite Undo/Redo
 
-To implement undo/redo, XML Notepad follows a common design pattern of Command objects with Undo and
-Redo methods. Commands operate on both a `TreeNode` and an `XmlNode` because some commands like
-`InsertNode` don't have an `XmlNode` yet until they are performed, but the command needs to know
-where in the tree this new node will be inserted and during `Undo` where it should be removed. The
-UndoManager collects these in a list. Then the state of the UndoManager controls the
-enabled/disabled state of the Undo/Redo MenuItems. When the user selects the Undo menu item, the
-Undo method is called on the active command, and that command is pushed onto the Redo stack.
+To implement undo/redo, XML Notepad follows a common design pattern of Command objects with Undo and Redo methods.
+Commands operate on both a `TreeNode` and an `XmlNode` because some commands like `InsertNode` don't have an `XmlNode`
+yet until they are performed, but the command needs to know where in the tree this new node will be inserted and during
+`Undo` where it should be removed. The UndoManager collects these in a list. Then the state of the UndoManager controls
+the enabled/disabled state of the Undo/Redo MenuItems. When the user selects the Undo menu item, the Undo method is
+called on the active command, and that command is pushed onto the Redo stack.
 
 ![undo.png](../assets/images/undo.png)
 
-Some operations in the editor cause many edits in the tree, including the replace-all operation and
-editing the value of a namespace attribute. (When you change the value of a namespace attribute,
-every XmlNode bound to that namespace needs to be reconstructed with a new namespace URI, which can
-obviously affect a lot of nodes in the tree!) So, to make these operations one atomic undo
-operation, there is a `CompoundCommand` object that contains a list of smaller edit commands, and
-this CompoundCommand is put into the `UndoManager`.
+Some operations in the editor cause many edits in the tree, including the replace-all operation and editing the value of
+a namespace attribute. (When you change the value of a namespace attribute, every XmlNode bound to that namespace needs
+to be reconstructed with a new namespace URI, which can obviously affect a lot of nodes in the tree!) So, to make these
+operations one atomic undo operation, there is a `CompoundCommand` object that contains a list of smaller edit commands,
+and this CompoundCommand is put into the `UndoManager`.
 
-Other simpler command objects include the following, which all operate on XmlTreeNode and XmlNode
-objects:
+Other simpler command objects include the following, which all operate on XmlTreeNode and XmlNode objects:
 
 ![commands.png](../assets/images/commands.png)
 
-The PasteCommand is special because it takes random XML text off the clipboard and parses it in
-the context of the currently selected element in the tree, inheriting the namespaces in scope. The
-helper class TreeData uses the special XmlTextReader constructor that takes an XmlParserContext as
-input.
+The PasteCommand is special because it takes random XML text off the clipboard and parses it in the context of the
+currently selected element in the tree, inheriting the namespaces in scope. The helper class TreeData uses the special
+XmlTextReader constructor that takes an XmlParserContext as input.
 
 ### Accessibility
 
-In order to make testing possible using `System.Windows.Automation`, there are some custom
-`AccessibleObject` implementations inside the TreeView and NodeTextView. See `AccessibleNode` and
-`AccessibleNodeTextViewNode`. These accessibility classes should also make Windows accessibility
-features work better with those custom views.
+In order to make testing possible using `System.Windows.Automation`, there are some custom `AccessibleObject`
+implementations inside the TreeView and NodeTextView. See `AccessibleNode` and `AccessibleNodeTextViewNode`. These
+accessibility classes should also make Windows accessibility features work better with those custom views.
 
 ### Missing Documentation?
 
-If you want more detailed documentation on some aspect of XML Notepad, please create a new [GitHub issue](https://github.com/microsoft/XmlNotepad/issues).
+If you want more detailed documentation on some aspect of XML Notepad, please create a new [GitHub
+issue](https://github.com/microsoft/XmlNotepad/issues).

docs/dev/index.md

@@ -6,8 +6,9 @@ XML Notepad targets [.NET Framework version 4.8](https://dotnet.microsoft.com/en
 
 ### Coding Guidelines
 
-XmlNotepad follows the standard [C# Coding Guidelines](https://docs.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions) with
-the default C# formatting settings that ship with VS 2022.
+XmlNotepad follows the standard [C# Coding
+Guidelines](https://docs.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions) with the
+default C# formatting settings that ship with VS 2022.
 
 The following additional conventions are also followed:
 
@@ -19,7 +20,8 @@ The following additional conventions are also followed:
 1. Constants are PascalCased even if they are private to a class.
 1. Try and collect all private fields at the top of the class.
 1. Public fields are PascalCased like public properties and methods.
-1. Generally one class per file, unless there is a super natural family of classes, like Commands.cs, that would cause an unnecessary explosion in number of files.
+1. Generally one class per file, unless there is a super natural family of classes, like Commands.cs, that would cause
+   an unnecessary explosion in number of files.
 1. Nice to have blank line between methods.
 1. Use "Remove and Sort Usings" command in VS.
 
@@ -63,78 +65,74 @@ After building the app:
 
 - Right click the `UnitTests` project and select `Run tests`.
 
-This is a GUI test, so do not move your mouse or type on your keyboard or let your
-screen lock until this test is completed.  Total test run time is about 12 minutes.
+This is a GUI test, so do not move your mouse or type on your keyboard or let your screen lock until this test is
+completed. Total test run time is about 12 minutes.
 
-The tests all pass on Windows 10, but currently some tests fail on Windows 11, there seems to be
-some breaking changes in the Windows Automation layer that XML notepad tests are using.  This is
-being investigated.
+The tests all pass on Windows 10, but currently some tests fail on Windows 11, there seems to be some breaking changes
+in the Windows Automation layer that XML notepad tests are using. This is being investigated.
 
-Note: [bug 10244](https://github.com/dotnet/winforms/issues/10244) is still open
-in in .net 4.8 System.Windows.Automation of menu items that blocks the tests, so
-checkout the branch `clovett/net472` to run the unit tests.
+Note: [bug 10244](https://github.com/dotnet/winforms/issues/10244) is still open in in .net 4.8
+System.Windows.Automation of menu items that blocks the tests, so checkout the branch `clovett/net472` to run the unit
+tests.
 
 ### UpdateVersions
 
-The `UpdateVersions` project synchronizes the `Version.props` information
-across multiple places so you can edit the version number in `Version.props` and this tool will
-replicate that across the following:
+The `UpdateVersions` project synchronizes the `Version.props` information across multiple places so you can edit the
+version number in `Version.props` and this tool will replicate that across the following:
 
 1. The `Version.cs` file which sets the assembly version for all projects in the solution.
 1. The WIX based setup file `Product.wxs`.
 2. The windows package manifest file `Package.appxmanifest`.
 3. The updates.xml file.
 4. The readme.htm file.
 
-You will also have to restart Visual Studio so that the new versions are picked up by the ClickOnce
-deployment information in  `Application.csproj`.
+You will also have to restart Visual Studio so that the new versions are picked up by the ClickOnce deployment
+information in  `Application.csproj`.
 
 ### Publish the app and all setups
 
 The `publish.cmd` script runs UpdateVersions, builds Release bits, builds the ClickOnce installer and the winget.msix
 installer from `XmlNotepadPackage`, and the standalone .msi installer from `XmlNotepadSetup`, it zips these files so
-they can be available on the Github Release page then it creates the new github release for the current version.  It
-also signs the assemblies and installers using the signing certificate specified by the environment variable
-`MYKEYFILE`.
+they can be available on the Github Release page then it creates the new github release for the current version. It also
+signs the assemblies and installers using the signing certificate specified by the environment variable `MYKEYFILE`.
 
 The ClickOnce installed is uploaded to
 [lovettsoftware](https://lovettsoftwarestorage.blob.core.windows.net/downloads/XmlNotepad/XmlNotepad.application) using
-the environment variable LOVETTSOFTWARE_STORAGE_CONNECTION_STRING.  Click once is convenient because it provides
+the environment variable LOVETTSOFTWARE_STORAGE_CONNECTION_STRING. Click once is convenient because it provides
 auto-updating whenever a new version is published.
 
 ### Build the setup .msi installer
 
-After building the `Release` configuration of `XmlNotepad.sln` load the `XmlNotepadSetup.sln`.  This
-solution uses the [WIX Toolset](https://wixtoolset.org/) to build a standalone windows .msi
-installer. To build that setup you will need to install the WIX toolset then the [Wix Toolset Visual
-Studio 2022
+After building the `Release` configuration of `XmlNotepad.sln` load the `XmlNotepadSetup.sln`. This solution uses the
+[WIX Toolset](https://wixtoolset.org/) to build a standalone windows .msi installer. To build that setup you will need
+to install the WIX toolset then the [Wix Toolset Visual Studio 2022
 Extension](https://marketplace.visualstudio.com/items?itemName=WixToolset.WixToolsetVisualStudio2022Extension).
 
-Then right click the `XmlNotepadSetup` project and select "build".  This will produce an .msi installer in the
-XmlNotepadSetup\bin\release folder.  There is also a `sign.cmd` script invoked by this build that will try and sign the
-resulting .msi using the certificate installed by the author.  This step will only work for the author who owns the
+Then right click the `XmlNotepadSetup` project and select "build". This will produce an .msi installer in the
+XmlNotepadSetup\bin\release folder. There is also a `sign.cmd` script invoked by this build that will try and sign the
+resulting .msi using the certificate installed by the author. This step will only work for the author who owns the
 certificate.
 
 This `msi` installer gives folks the option to install XML Notepad on machines that are isolated from the internet and
 there are quite a few customers who have requested this, which is why it exists.
 
 ### Build the winget setup package
 
-The `winget` setup package is built by the `XmlNotepadPackage` project in the `XmlNotepadSetup.sln`
-solution.  Right click this project in the Solution Explorer and select `Publish` and `Create App
-Packages`.  Choose Sideloading, and the package files will be written to the
-XmlNotepadPackage\AppPackages folder.  These can then be uploaded to the server hosting these
-packages and you can then update the manifest in
+The `winget` setup package is built by the `XmlNotepadPackage` project in the `XmlNotepadSetup.sln` solution. Right
+click this project in the Solution Explorer and select `Publish` and `Create App Packages`. Choose Sideloading, and the
+package files will be written to the XmlNotepadPackage\AppPackages folder. These can then be uploaded to the server
+hosting these packages and you can then update the manifest in
 [winget-pkgs](https://github.com/microsoft/winget-pkgs/tree/master/manifests/m/Microsoft/XMLNotepad).
 
 This package provides the `winget install xmlnotepad` setup option.
 
 ### Publishing the bits to Azure Blob Store
 
-The `publish.cmd` script uses the [AzurePublishClickOnce](https://github.com/clovett/tools/tree/master/AzurePublishClickOnce) tool
-which uses the environment variable named `LOVETTSOFTWARE_STORAGE_CONNECTION_STRING` to access the Azure storage account
-where it uploads the new clickonce installer, and removes the older versions so that the storage account does not
-keep growing and growing.
+The `publish.cmd` script uses the
+[AzurePublishClickOnce](https://github.com/clovett/tools/tree/master/AzurePublishClickOnce) tool which uses the
+environment variable named `LOVETTSOFTWARE_STORAGE_CONNECTION_STRING` to access the Azure storage account where it
+uploads the new clickonce installer, and removes the older versions so that the storage account does not keep growing
+and growing.
 
 ### Design
 
@@ -143,5 +141,5 @@ See [XML Notepad Design ](design.md) for more detailed information about how thi
 ### Issues
 
 Feedback and suggestions are welcome, just use the [GitHub  issues
-list](https://github.com/microsoft/XmlNotepad/issues).  Pull requests are also welcome, in fact, a number of good pull
-requests have already been merged.  Thanks to all who are helping to make XML notepad a great tool!
+list](https://github.com/microsoft/XmlNotepad/issues). Pull requests are also welcome, in fact, a number of good pull
+requests have already been merged. Thanks to all who are helping to make XML notepad a great tool!