Polished contributing docs (#10299)

Co-authored-by: Trask Stalnaker <[email protected]>

Author: steverao

docs/contributing/muzzle.md

@@ -144,7 +144,7 @@ instrumented application.
 The easiest way it can be done is by adding `assertInverse.set(true)` to the `pass` muzzle
 directive. The plugin will add an implicit `fail` directive that contains all other versions of the
 instrumented library.
-It is worth using `assertInverse.set(true)` by default when writing instrumentation modules, even for
+You SHOULD use `assertInverse.set(true)` when writing instrumentation modules, even for
 very old library versions. The muzzle plugin will ensure that those old versions won't be
 accidentally instrumented when we know that the instrumentation will not work properly for them.
 Having a `fail` directive forces the authors of the instrumentation module to properly specify

docs/contributing/writing-instrumentation.md

@@ -45,7 +45,7 @@ may be restricted by the interception APIs provided by the library.
 Within the subfolder, create three folders `library` (skip if library instrumentation is not
 possible),`javaagent`, and `testing`.
 
-For example, if you are targeting the RPC framework `yarpc` at version `1.0`, you would have a
+For example, if you are targeting the RPC framework `yarpc` at minimal supported version `1.0`, you would have a
 directory tree like the following:
 
 ```
@@ -60,7 +60,7 @@ instrumentation ->
             build.gradle.kts
 ```
 
-The top level `settings.gradle.kts` file would contain the following:
+The top level `settings.gradle.kts` file would contain the following (please add in alphabetical order):
 
 ```kotlin
 include("instrumentation:yarpc-1.0:javaagent")