Reflow of all markdown files

CODE_OF_CONDUCT.md

@@ -2,10 +2,11 @@
 
 ## Our Pledge
 
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making
-participation in our project and our community a harassment-free experience for everyone, regardless of age, body size,
-disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race,
-religion, or sexual identity and orientation.
+In the interest of fostering an open and welcoming environment, we as contributors and
+maintainers pledge to making participation in our project and our community a
+harassment-free experience for everyone, regardless of age, body size, disability,
+ethnicity, gender identity and expression, level of experience, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
 
 ## Our Standards
 
@@ -22,39 +23,47 @@ Examples of unacceptable behavior by participants include:
 * The use of sexualized language or imagery and unwelcome sexual attention or advances
 * Trolling, insulting/derogatory comments, and personal or political attacks
 * Public or private harassment
-* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Publishing others' private information, such as a physical or electronic address, without
+  explicit permission
 * Other conduct which could reasonably be considered inappropriate in a professional setting
 
 ## Our Responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate
-and fair corrective action in response to any instances of unacceptable behavior.
+Project maintainers are responsible for clarifying the standards of acceptable behavior and
+are expected to take appropriate and fair corrective action in response to any instances of
+unacceptable behavior.
 
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues,
-and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor
-for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+Project maintainers have the right and responsibility to remove, edit, or reject comments,
+commits, code, wiki edits, issues, and other contributions that are not aligned to this Code
+of Conduct, or to ban temporarily or permanently any contributor for other behaviors that
+they deem inappropriate, threatening, offensive, or harmful.
 
 ## Scope
 
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project
-or its community. Examples of representing a project or community include using an official project e-mail address, posting
-via an official social media account, or acting as an appointed representative at an on-line or off-line event. Representation
-of a project may be further defined and clarified by project maintainers.
+This Code of Conduct applies both within project spaces and in public spaces when an
+individual is representing the project or its community. Examples of representing a project
+or community include using an official project e-mail address, posting via an official
+social media account, or acting as an appointed representative at an on-line or off-line
+event. Representation of a project may be further defined and clarified by project
+maintainers.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at
-osscodeofconduct@telliam.com. The project team will review and investigate all complaints, and will respond in a way that
-it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the
-reporter of an incident. Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by
+contacting the project team at osscodeofconduct@telliam.com. The project team will review
+and investigate all complaints, and will respond in a way that it deems appropriate to the
+circumstances. The project team is obligated to maintain confidentiality with regard to the
+reporter of an incident. Further details of specific enforcement policies may be posted
+separately.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions
-as determined by other members of the project's leadership.
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face
+temporary or permanent repercussions as determined by other members of the project's
+leadership.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at
-[http://contributor-covenant.org/version/1/4][version]
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
 
 [homepage]: http://contributor-covenant.org
 [version]: http://contributor-covenant.org/version/1/4/

GOVERNANCE.md

@@ -3,60 +3,67 @@ This document describes the governance model for this project.
 (This is adapted from the template provided by http://oss-watch.ac.uk/resources/benevolentdictatorgovernancemodel )
 
 ## Overview
-This project is led by a benevolent dictator and managed by the community. That is, the community actively contributes
-to the day-to-day maintenance of the project, but the general strategic line is drawn by the benevolent dictator. In
-case of disagreement, they have the last word. It is the benevolent dictator's job to resolve disputes within the
-community and to ensure that the project is able to progress in a coordinated way. In turn, it is the community's job
-to guide the decisions of the benevolent dictator through active engagement and contribution.
+This project is led by a benevolent dictator and managed by the community. That is, the
+community actively contributes to the day-to-day maintenance of the project, but the general
+strategic line is drawn by the benevolent dictator. In case of disagreement, they have the
+last word. It is the benevolent dictator's job to resolve disputes within the community and
+to ensure that the project is able to progress in a coordinated way. In turn, it is the
+community's job to guide the decisions of the benevolent dictator through active engagement
+and contribution.
 
 ## Roles and responsibilities
 ### Benevolent dictator (project lead)
 
-Typically, the benevolent dictator, or project lead, is self-appointed. However, because the community always has the
-ability to fork, this person is fully answerable to the community. The project lead's role is a
-[difficult one](http://producingoss.com/html-chunk/social-infrastructure.html#benevolent-dictator-qualifications): they
-set the strategic objectives of the project and communicate these clearly to the community. They also have to understand
-the community as a whole and strive to satisfy as many conflicting needs as possible, while ensuring that the project
-survives in the long term.
-
-In many ways, the role of the benevolent dictator is less about dictatorship and more about diplomacy. The key is to
-ensure that, as the project expands, the right people are given influence over it and the community rallies behind the
-vision of the project lead. The lead's job is then to ensure that the committers (see below) make the right decisions
-on behalf of the project. Generally speaking, as long as the committers are aligned with the project's strategy, the
-project lead will allow them to proceed as they desire.
+Typically, the benevolent dictator, or project lead, is self-appointed. However, because the
+community always has the ability to fork, this person is fully answerable to the community.
+The project lead's role is a [difficult one](http://producingoss.com/html-chunk/social-infrastructure.html#benevolent-dictator-qualifications):
+they set the strategic objectives of the project and communicate these clearly to the
+community. They also have to understand the community as a whole and strive to satisfy as
+many conflicting needs as possible, while ensuring that the project survives in the long
+term.
+
+In many ways, the role of the benevolent dictator is less about dictatorship and more about
+diplomacy. The key is to ensure that, as the project expands, the right people are given
+influence over it and the community rallies behind the vision of the project lead. The
+lead's job is then to ensure that the committers (see below) make the right decisions on
+behalf of the project. Generally speaking, as long as the committers are aligned with the
+project's strategy, the project lead will allow them to proceed as they desire.
 
 ### Committers
 
-Committers are contributors who have made several valuable contributions to the project and are now relied upon to
-both write code directly to the repository and screen the contributions of others. In many cases they are programmers
-but it is also possible that they contribute in a different role. Typically, a committer will focus on a specific aspect
-of the project, and will bring a level of expertise and understanding that earns them the respect of the community and
-the project lead. The role of committer is not an official one, it is simply a position that influential members of the
-community will find themselves in as the project lead looks to them for guidance and support.
-
-Committers have no authority over the overall direction of the project. However, they do have the ear of the project
-lead. It is a committer's job to ensure that the lead is aware of the community's needs and collective objectives, and
-to help develop or elicit appropriate contributions to the project. Often, committers are given informal control over
-their specific areas of responsibility, and are assigned rights to directly modify certain areas of the source code.
-That is, although committers do not have explicit decision-making authority, they will often find that their actions
-are synonymous with the decisions made by the lead.
+Committers are contributors who have made several valuable contributions to the project and
+are now relied upon to both write code directly to the repository and screen the
+contributions of others. In many cases they are programmers but it is also possible that
+they contribute in a different role. Typically, a committer will focus on a specific aspect
+of the project, and will bring a level of expertise and understanding that earns them the
+respect of the community and the project lead. The role of committer is not an official one,
+it is simply a position that influential members of the community will find themselves in as
+the project lead looks to them for guidance and support.
+
+Committers have no authority over the overall direction of the project. However, they do
+have the ear of the project lead. It is a committer's job to ensure that the lead is aware
+of the community's needs and collective objectives, and to help develop or elicit
+appropriate contributions to the project. Often, committers are given informal control over
+their specific areas of responsibility, and are assigned rights to directly modify certain
+areas of the source code. That is, although committers do not have explicit decision-making
+authority, they will often find that their actions are synonymous with the decisions made by
+the lead.
 
 ### Contributors
 
-Contributors are community members who either have no desire to become committers, or have not yet been given the
-opportunity by the benevolent dictator. They make valuable contributions, such as those outlined in the list below,
-but generally do not have the authority to make direct changes to the project code. Contributors engage with the
-project through communication tools, such as email lists, and via reports and
-[patches](http://oss-watch.ac.uk/resources/softwarepatch) attached to issues in the issue tracker, as detailed in
-our [community tools document](http://oss-watch.ac.uk/resources/communitytools).
-
-Anyone can become a contributor. There is no expectation of commitment to the project, no specific skill requirements
-and no selection process. To become a contributor, a community member simply has to perform one or more actions that
-are beneficial to the project.
+Contributors are community members who either have no desire to become committers, or have
+not yet been given the opportunity by the benevolent dictator. They make valuable
+contributions, such as those outlined in the list below, but generally do not have the
+authority to make direct changes to the project code. Contributors engage with the project
+through communication tools, such as email lists, and via reports and [patches](http://oss-watch.ac.uk/resources/softwarepatch)
+attached to issues in the issue tracker, as detailed in our [community tools document](http://oss-watch.ac.uk/resources/communitytools).
 
-Some contributors will already be engaging with the project as users, but will also find themselves doing one or more
-of the following:
+Anyone can become a contributor. There is no expectation of commitment to the project, no
+specific skill requirements and no selection process. To become a contributor, a community
+member simply has to perform one or more actions that are beneficial to the project.
 
+Some contributors will already be engaging with the project as users, but will also find
+themselves doing one or more of the following:
 * Supporting new users (current users often provide the most effective new user support)
 * Reporting bugs
 * Identifying requirements
@@ -67,44 +74,52 @@ of the following:
 * Fixing bugs
 * Adding features
 
-As contributors gain experience and familiarity with the project, they may find that the project lead starts relying
-on them more and more. When this begins to happen, they gradually adopt the role of committer, as described above.
+As contributors gain experience and familiarity with the project, they may find that the
+project lead starts relying on them more and more. When this begins to happen, they
+gradually adopt the role of committer, as described above.
 
 ### Users
 
-Users are community members who have a need for the project. They are the most important members of the community:
-without them, the project would have no purpose. Anyone can be a user; there are no specific requirements.
+Users are community members who have a need for the project. They are the most important
+members of the community:
+without them, the project would have no purpose. Anyone can be a user; there are no specific
+requirements.
 
-Users should be encouraged to participate in the life of the project and the community as much as possible. User
-contributions enable the project team to ensure that they are satisfying the needs of those users. Common user
-activities include (but are not limited to):
+Users should be encouraged to participate in the life of the project and the community as
+much as possible. User contributions enable the project team to ensure that they are
+satisfying the needs of those users. Common user activities include (but are not limited to):
 
 * Evangelizing about the project
 * Informing developers of project strengths and weaknesses from a new user's perspective
 * Providing moral support (a 'thank you' goes a long way)
 * Providing financial support
 
-Users who continue to engage with the project and its community will often find themselves becoming more and more
-involved. Such users may then go on to become contributors, as described above.
+Users who continue to engage with the project and its community will often find themselves
+becoming more and more involved. Such users may then go on to become contributors, as
+described above.
 
 ### Support
 
-All participants in the community are encouraged to provide support for new users within the project management
-infrastructure. This support is provided as a way of growing the community. Those seeking support should recognize that
-all support activity within the project is voluntary and is therefore provided as and when time allows. A user requiring
-guaranteed response times or results should therefore seek to purchase a support contract from a vendor. (Of course,
-that vendor should be an active member of the community.) However, for those willing to engage with the project on its
-own terms, and willing to help support other users, the community support channels are ideal.
+All participants in the community are encouraged to provide support for new users within the
+project management infrastructure. This support is provided as a way of growing the
+community. Those seeking support should recognize that all support activity within the
+project is voluntary and is therefore provided as and when time allows. A user requiring
+guaranteed response times or results should therefore seek to purchase a support contract
+from a vendor. (Of course, that vendor should be an active member of the community.)
+However, for those willing to engage with the project on its own terms, and willing to help
+support other users, the community support channels are ideal.
 
 ### Contribution process
 
-Anyone can contribute to the project, regardless of their skills, as there are many ways to contribute. For instance, a
-contributor might be active on the project mailing list and issue tracker, or might supply
-[patches](http://oss-watch.ac.uk/resources/softwarepatch). The various ways of contributing are described in more detail
-in our [roles in open source document](http://oss-watch.ac.uk/resources/rolesinopensource).
+Anyone can contribute to the project, regardless of their skills, as there are many ways to
+contribute. For instance, a contributor might be active on the project mailing list and
+issue tracker, or might supply [patches](http://oss-watch.ac.uk/resources/softwarepatch).
+The various ways of contributing are described in more detail in our
+[roles in open source document](http://oss-watch.ac.uk/resources/rolesinopensource).
 
 ### Decision-making process
 
-The benevolent dictatorship model does not need a formal conflict resolution process, since the project lead's word is
-final. If the community chooses to question the wisdom of the actions of a committer, the project lead can review their
-decisions by checking the communication archives, and either uphold or reverse them.
+The benevolent dictatorship model does not need a formal conflict resolution process, since
+the project lead's word is final. If the community chooses to question the wisdom of the
+actions of a committer, the project lead can review their decisions by checking the
+communication archives, and either uphold or reverse them.

OneFlow/ReadMe.md

@@ -1,8 +1,8 @@
 # GIT OneFlow support scripts
 The scripts in this folder are used for release and feature branch management.
 This repository follows the [OneFlow](https://www.endoflineblog.com/oneflow-a-git-branching-model-and-workflow#develop-finishing-a-release-branch)
-model and work-flow. With one active long term branch 'develop'. The master
-branch is present and long term but is not active, it only points to the latest
-official release (including preview releases) of the project. This is a convenience
-to allow getting the latests released source quickly. Generally the scripts used here
-are only for release managers and are not required (or even an option) for most contributors.
+model and work-flow. With one active long term branch 'develop'. The master branch is
+present and long term but is not active, it only points to the latest official release
+(including preview releases) of the project. This is a convenience to allow getting the
+latests released source quickly. Generally the scripts used here are only for release
+managers and are not required (or even an option) for most contributors.

docfx/CommandLine/api/index.md

@@ -1,3 +1,3 @@
 # About
-Ubiquity.NET.CommandLines contains general extensions for .NET. to support command line
+`Ubiquity.NET.CommandLine` contains general extensions for .NET. to support command line
 parsing using `System.CommandLine`