Address review feedback

Signed-off-by: timflannagan <[email protected]>

Author: timflannagan

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # How to contribute
 
-Operator Lifecycle Manager is an Apache 2.0 licensed project and accepts contributions via GitHub pull requests. This document outlines some of the conventions on commit message formatting, contact points for developers, and other resources to help get contributions into the operator-lifecycle-manager project.
+Operator Lifecycle Manager (OLM) is an Apache 2.0 licensed project and accepts contributions via GitHub pull requests. This document outlines some of the conventions on commit message formatting, contact points for developers, and other resources to help get contributions into the OLM project.
 
 ## Communication
 
@@ -15,9 +15,9 @@ Operator Lifecycle Manager is an Apache 2.0 licensed project and accepts contrib
 
 ## Reporting bugs and creating issues
 
-Reporting bugs is one of the best ways to contribute. However, a good bug report has some very specific qualities, so please read over our short document on [reporting bugs](./doc/dev/reporting_bugs.md) before submitting a bug report. Before filing a bug report, ensure the bug hasn't already been reported by searching through the operator-lifecycle-manager project [Issues][issues].
+Reporting bugs is one of the best ways to contribute. However, a good bug report has some very specific qualities, so please read over our short document on [reporting bugs](./doc/dev/reporting_bugs.md) before submitting a bug report. Before filing a bug report, ensure the bug hasn't already been reported by searching through the OLM project [Issues][issues].
 
-Any new contribution should be accompanied by a new or existing issue. This issue can help track work, discuss the design and implementation, and help avoid wasted efforts or multiple people working on the same issue, compared to submitting a PR first. Trivial changes, like fixing a typo in the documentation, do not require the creation of a new issue. Proposing larger changes to the operator-lifecycle-manager project may require an enhancement be created in the [operator-framework/enhancements](https://github.com/operator-framework/enhancements/) repository.
+Any new contribution should be accompanied by a new or existing issue. This issue can help track work, discuss the design and implementation, and help avoid wasted efforts or multiple people working on the same issue, compared to submitting a PR first. Trivial changes, like fixing a typo in the documentation, do not require the creation of a new issue. Proposing larger changes to the OLM project may require an enhancement be created in the [operator-framework/enhancements](https://github.com/operator-framework/enhancements/) repository.
 
 ## Contribution flow
 
@@ -36,25 +36,33 @@ Thanks for contributing!
 
 ### Code Review
 
+<!--
+TODO(tflannag): Call out the need to run `make verify` locally for relevant codepaths.
+-->
+
 Each PR must be labeled with at least one "lgtm" label and at least one "approved" label before it can be merged.
 
 Maintainers that have approval permissions are listed in the "approvers" column in the root [OWNERS][owners] file.
 
 ### Code style
 
-The coding style suggested by the Golang community is used in the operator-lifecycle-manager project. See the [style doc](https://github.com/golang/go/wiki/CodeReviewComments) for details.
+The coding style suggested by the Golang community is used in the OLM project. See the [style doc](https://github.com/golang/go/wiki/CodeReviewComments) for details.
+
+In addition to the linked style documentation, OLM formats Golang packages using the `go fmt` tool. Before submitting a PR, please run `go fmt ...` on relevant packages and commit the results. This will help expedite the review process, focusing less on style conflicts, and more on the design and implementation details.
 
-Please follow this style to make the operator-lifecycle-manager project easier to review, maintain and develop.
+Please follow this style to make the OLM project easier to review, maintain and develop.
 
 ### Sign-off ([DCO][DCO])
 
 A [sign-off][sign-off] is a line towards the end of a commit message that certifies the commit author(s).
 
+For more information on the structuring of commit messages, read the information in the [DCO][https://github.com/apps/dco] application that the OLM projects uses.
+
 ## Documentation
 
 If the contribution changes the existing APIs or user interface it must include sufficient documentation to explain the use of the new or updated feature.
 
-The operator-lifecycle-manager documentation mainly lives in the [operator-framework/olm-docs][olm-docs] repository.
+The OLM documentation mainly lives in the [operator-framework/olm-docs][olm-docs] repository.
 
 [operator_framework]: https://groups.google.com/forum/#!forum/operator-framework
 [dco]: <https://developercertificate.org/>