[ovs-dev,3/3] ovsdb.5.rst: Fix minor format problem.
diff mbox series

Message ID 1566508103-22962-3-git-send-email-hzhou8@ebay.com
State New
Headers show
  • [ovs-dev,1/3] raft.c: Election timer initial reset with value from log.
Related show

Commit Message

Han Zhou Aug. 22, 2019, 9:08 p.m. UTC
From: Han Zhou <hzhou8@ebay.com>

Signed-off-by: Han Zhou <hzhou8@ebay.com>
 Documentation/ref/ovsdb.5.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff mbox series

diff --git a/Documentation/ref/ovsdb.5.rst b/Documentation/ref/ovsdb.5.rst
index bb35eee..46d268c 100644
--- a/Documentation/ref/ovsdb.5.rst
+++ b/Documentation/ref/ovsdb.5.rst
@@ -156,7 +156,7 @@  The clustered format has the following additional notation:
     2. The second element is either a transaction record in the format
-       described under ``Standalone Format'' above, or ``null``.
+       described under ``Standalone Format`` above, or ``null``.
     When a schema is present, the transaction record is relative to an empty
     database.  That is, a schema change effectively resets the database to
@@ -173,7 +173,7 @@  all of which are required, except ``prev_election_timer``:
     The address on which the server listens for connections from other
     servers in the cluster.
-``name": <id>``
+``"name": <id>``
     The database schema name.  It is only important when a server is in the
     process of joining a cluster: a server will only join a cluster if the
     name matches.  (If the database schema name were unique, then we would