fix README

Author: zapster

substratevm/src/com.oracle.svm.native.libcontainer/README.md

@@ -32,18 +32,19 @@ the OpenJDK, it should be updated regularly to profit from upstream fixes and im
 track of this, `ContainerLibrary.java` contains `@BasedOnJDKFile` annotations for each imported file,
 which links to the source version in the JDK. With this information, all upstream changes can be
 detected. Note that strictly speaking, the referenced version in the annotation does not necessarily
-mean that the file was imported, but rather that all changes have been reviewed. If there are changes
-that are irrelevant for `libsvm_container`, we might keep the file as is and still bump the version.
-That said, we plan to do full reimports regularly, at least once every for every release.
+mean that the file was imported from that revision. Rather that all changes have been reviewed. If
+there are changes that are irrelevant for `libsvm_container`, we might keep the file as is and still
+bump the version. That said, we plan to do full reimports regularly, at least once every for every
+release.
 
 To help keeping the `@BasedOnJDKFile` annotations up to date, the
 `mx gate --tags check_libcontainer_annotations` command ensures that the actual files and
 annotations are in sync.
 
 To do a full reimport, replace the files in [`src/hotspot`](./src/hotspot) with those from the OpenJDK.
 The `mx reimport-libcontainer-files --jdk-repo path/to/jdk` can help with that. Then reapply all the
-changes (`#ifdef` guards) using the diff tool of your choice. Finally, adopt the files in
-[`src/svm`](./src/svm) to provide new functionality, if needed. Finally, the `@BasedOnJDKFile`
+changes (`#ifdef` guards) using the diff tool of your choice. Then, adopt the files in
+[`src/svm`](./src/svm) to provide new functionality, if needed. Finally, update the `@BasedOnJDKFile`
 annotations in `ContainerLibrary.java` to reflect the import revision.
 
 ## Local Testing