coder
diff --git a/‎CONTRIBUTING.md renamed to ‎docs/CONTRIBUTING.md
Lines changed: 2 additions & 2 deletions b/‎CONTRIBUTING.md renamed to ‎docs/CONTRIBUTING.md
Lines changed: 2 additions & 2 deletions
diff --git a/‎README.md renamed to ‎docs/README.md b/‎README.md renamed to ‎docs/README.md
@@ -6,13 +6,13 @@ Contributions must adhere to [Effective Go](https://go.dev/doc/effective_go). Ad
 
 ### No Unused Packages
 
-Coders write packages that are used during implementation. It's difficult to validate whether an abstraction is valid until it's checked against an implementation. This results in a larger changeset, but provides reviewers with an educated perspective on the contribution.
+Coders write packages that are used during implementation. It's difficult to validate whether an abstraction is valid until it's checked against an implementation. This results in a larger changeset but provides reviewers with an educated perspective on the contribution.
 
 ## Review
 
 > Taken from [Go's review philosophy](https://go.dev/doc/contribute#reviews).
 
-Coders value very thorough reviews. Think of each review comment like a ticket: you are expected to somehow "close" it by acting on it, either by implementing the suggestion or convincing the reviewer otherwise.
+Coders value thorough reviews. Think of each review comment like a ticket: you are expected to somehow "close" it by acting on it, either by implementing the suggestion or convincing the reviewer otherwise.
 
 After you update the change, go through the review comments and make sure to reply to every one. You can click the "Done" button to reply indicating that you've implemented the reviewer's suggestion; otherwise, click on "Reply" and explain why you have not, or what you have done instead.