Skip to content

Commit 9e86de6

Browse files
authored
Fix list-table markup issues (#1629)
1 parent db320ca commit 9e86de6

File tree

2 files changed

+10
-10
lines changed

2 files changed

+10
-10
lines changed

source/reference/command.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -683,7 +683,7 @@ Administration Commands
683683

684684
- Retrieves cluster parameter values from all nodes in a cluster.
685685

686-
.. versionadded:: 6.0
686+
.. versionadded:: 6.0
687687

688688
* - :dbcommand:`getParameter`
689689

source/reference/command/getLog.txt

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -64,15 +64,15 @@ The possible values for :dbcommand:`getLog` are:
6464
:binary:`~bin.mongod` started without warnings, this filter
6565
may return an empty array.
6666

67-
.. note::
68-
69-
Starting in MongoDB 4.4, the :dbcommand:`getLog` command no longer
70-
accepts the ``rs`` value, as this categorization of message type
71-
has been deprecated. Instead, log messages are now always
72-
identified by their :ref:`component <log-message-components>` -
73-
including *REPL* for replication messages. See
74-
:ref:`log-message-parsing-example-filter-component` for log
75-
parsing examples that filter on the component field.
67+
.. note::
68+
69+
Starting in MongoDB 4.4, the :dbcommand:`getLog` command no longer
70+
accepts the ``rs`` value, as this categorization of message type
71+
has been deprecated. Instead, log messages are now always
72+
identified by their :ref:`component <log-message-components>` -
73+
including *REPL* for replication messages. See
74+
:ref:`log-message-parsing-example-filter-component` for log
75+
parsing examples that filter on the component field.
7676

7777
Output
7878
------

0 commit comments

Comments
 (0)