Apply suggestions from docs review

Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>

Author: jcogs33

java/ql/src/Likely Bugs/Frameworks/JUnit/JUnit5MissingNestedAnnotation.md

@@ -1,6 +1,6 @@
 ## Overview
 
-JUnit tests are grouped in a class, and starting from JUnit 5 users can group the test classes in a bigger class so they can share the local environment of the enclosing class. While this helps to organize the unit tests and foster code reuse, if an inner test class is not annotated with `@Nested`, the unit tests in it will fail to execute during builds.
+JUnit tests are grouped in a class, and starting from JUnit 5, users can group the test classes in a larger class so they can share the local environment of the enclosing class. While this helps organize the unit tests and foster code reuse, if an inner test class is not annotated with `@Nested`, the unit tests in it will fail to execute during builds.
 
 ## Recommendation
 

java/ql/src/Likely Bugs/Frameworks/JUnit/JUnit5MissingNestedAnnotation.ql

@@ -3,7 +3,7 @@
  * @previous-id java/junit5-non-static-inner-class-missing-nested-annotation
  * @name Missing `@Nested` annotation on JUnit 5 inner test class
  * @description A JUnit 5 inner test class that is missing a `@Nested` annotation will be
- *              excluded from execution and it may indicate a misunderstanding from the
+ *              excluded from execution and may indicate a mistake from the
  *              programmer.
  * @kind problem
  * @precision very-high