doc: typo / grammar pass on OSPF API docs

Signed-off-by: Quentin Young <qlyoung@cumulusnetworks.com>

diff --git a/doc/developer/ospf-api.rst b/doc/developer/ospf-api.rst
index f9f511ef877af8ec721aa58b8dae2d83596b875b..41c31b29c3dd80d7ef967cdedd91d7ac6d6563c0 100644 (file)
--- a/doc/developer/ospf-api.rst
+++ b/doc/developer/ospf-api.rst
@@ -246,8 +246,8 @@ Important note:
 ^^^^^^^^^^^^^^^
 
 In order to originate an opaque LSA, there must be at least one active
-opaque-capable neighbor. Thus, you cannot originate opaque LSAs of no neighbors
-are present. If you try to originate even so no neighbor is ready, you will
+opaque-capable neighbor. Thus, you cannot originate opaque LSAs if no neighbors
+are present. If you try to originate when no neighbors are ready, you will
 receive a not ready error message. The reason for this restriction is that it
 might be possible that some routers have an identical opaque LSA from a
 previous origination in their LSDB that unfortunately could not be flushed due
@@ -320,7 +320,8 @@ The synchronous requests and replies have the following message formats:
 
    image
 
-The origin field allows to select according to the following types of origins:
+The origin field allows origin-based filtering using the following origin
+types:
 
 +-------------------------+---------+
 | Origin                  | Value   |
@@ -332,7 +333,7 @@ The origin field allows to select according to the following types of origins:
 | ANY\_ORIGIN             | 2       |
 +-------------------------+---------+
 
-The reply message has on of the following error codes:
+The reply message has one of the following error codes:
 
 +--------------------------+---------+
 | Error code               | Value   |
@@ -365,6 +366,9 @@ The asynchronous notifications have the following message formats:
 
    image
 
+
+.. Do not delete these acknowledgements!
+
 Original Acknowledgments from Ralph Keller
 ------------------------------------------