Update docs/contributing/contributing-code/contributing-code-writing/…

…README.md

Co-authored-by: Yetkin Timocin <[email protected]>

docs/contributing/contributing-code/contributing-code-writing/README.md

@@ -44,7 +44,7 @@ We also *mostly* agree with [Google's Go Style Guide](https://google.github.io/s
 
 One thing we do require is [godoc comments](https://tip.golang.org/doc/comment) on **exported** packages, types, variables, constants, and functions. We like this because it has two good effects:
 
-- Encourages you to be minimize the exported surface-area, thus simplifying the design.
+- Encourages you to minimize the exported surface-area, thus simplifying the design.
 - Requires you to document clearly the purpose code you expect other parts of the codebase to call.
 
 Right now we don't have automated enforcement of this rule, so expect it to come up in code review if you forget.