[pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

common-practices-tools/contribution/contrib-first.md

@@ -9,8 +9,8 @@ Whenever we are building something that could be of use by more than one project
 ## Rationale for contrib first
 
 -   **Fiscal responsibility** - Building it and contributing it means that other government agencies will never have to pay to build the same thing twice. This helps agencies comply with Federal Source Code Policy: Achieving Efficiency, Transparency, and Innovation through Reusable and Open Source Software [OMB Memorandum M-16-21](https://obamawhitehouse.archives.gov/sites/default/files/omb/memoranda/2016/m_16_21.pdf)
--   **Reusability** - CivicActions other clients  and the public at large can benefit from work that was already done.
--   **Security** - contributing our work to an open source project like Drupal means it may receive security coverage by the Drupal security team and the public.  It is made more secure by getting more eyes on the code and more users surfacing any issues.
+-   **Reusability** - CivicActions other clients and the public at large can benefit from work that was already done.
+-   **Security** - contributing our work to an open source project like Drupal means it may receive security coverage by the Drupal security team and the public. It is made more secure by getting more eyes on the code and more users surfacing any issues.
 -   **Avoiding the gift that never happens** - Clients are not typically supportive of taking working local software that was already built for them and in use by them, and then paying to move or refactor that software to become open source. The benefit is too small for the cost. By building it as contributed code first, there is no extra cost.
 -   **Development happens in the open** - The issues are public. The commits are public. Everyone can contribute improvements.
 -   **Reliability** - A solution built for contribution is often better designed, and better documented than a local solution meant to "just get it done". By putting our company and personal names on it publicly we commit to a quality product. Releasing a FOSS solution also increases the number of testers and edge cases that can surface and reduce bugs in the code.
@@ -24,7 +24,7 @@ Whenever we are building something that could be of use by more than one project
 -   [Codit: Menu Tools](https://www.drupal.org/project/codit_menu_tools)
 -   [Content Model & Site Documentation](https://www.drupal.org/project/content_model_documentation)
 -   [Drupal Knowledge Archive Network (DKAN Open Data Portal)](https://github.com/GetDKAN/dkan)
-    - [CMSDS Open Data Components](https://github.com/GetDKAN/cmsds-open-data-components)
+    -   [CMSDS Open Data Components](https://github.com/GetDKAN/cmsds-open-data-components)
 -   [Drydock Cloud](https://github.com/drydockcloud)
 -   [Entity Field Fetch field](https://www.drupal.org/project/entity_field_fetch)
 -   [GovDelivery Bulletins](https://www.drupal.org/project/govdelivery_bulletins)

practice-areas/engineering/drupal/drupal-contrib-first-module-development.md

@@ -14,6 +14,7 @@ When a new module is needed we try to follow [Contrib First](../../../common-pra
     - Choose a meaningful search engine friendly module name. (crowd sourcing name suggestions is recommended)
     - Create the Drupal project on Drupal.org
     - Populate the project page with a description of what is coming. List supporters as CivicActions and the client [directions](./README.md#contribution-to-drupalorg-modules-and-themes). If the client does not have a drupal.org page, get help from your PM to encourage them to create one.
+
 5. Populate the issue queue on the Drupal project with "Feature requests". Keep them as atomic as possible. Mark any that are part of the MVP as "major". Create issues for any improvement ideas that pop up. They don't all have to be acted on, but they help shape the road map for where you want the module to go.
 6. Close the issues as you go and be sure to credit yourself, CivicActions, and the client.
 7. Begin with alpha releases. Ideally when all your MVP/major issues are closed, you are ready for the official release.