manual fix until release (#587)

Author: PingDavidR

docs/docker-images/pingdirectory/README.md

@@ -103,7 +103,7 @@ You can view the Docker logs with the command:
 You should see the ouptut from a PingDirectory install and configuration, ending with a message the the PingDirectory has started.  After it starts, you will see some typical access logs.  Simply ``Ctrl-C`` after to stop tailing the logs.
 
 ## Running a sample 100/sec search rate test
-With the PingDirectory running from the previous section, you can run a ``searchrate`` job that will send load to the directory at a rate if 100/sec using the following command.
+With the PingDirectory running from the previous section, you can run a ``searchrate`` job that will send load to the directory at a rate of 100/sec using the following command.
 
 ```
 docker exec -it pingdirectory \

docs/docker-images/pingdirectoryproxy/README.md

@@ -92,7 +92,7 @@ You can view the Docker logs with the command:
 You should see the output from a PingDirectoryProxy install and configuration, ending with a message the the PingDirectoryProxy has started.  After it starts, you will see some typical access logs.  Simply ``Ctrl-C`` after to stop tailing the logs.
 
 ## Running a sample 100/sec search rate test
-With the PingDirectoryProxy running from the previous section, you can run a ``searchrate`` job that will send load to the directory at a rate if 100/sec using the following command.
+With the PingDirectoryProxy running from the previous section, you can run a ``searchrate`` job that will send load to the directory at a rate of 100/sec using the following command.
 
 ```
 docker exec -it pingdirectoryproxy \