Skip to content

Copy edits for typos #2208

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion source/reference/method/rs.reconfig.txt
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ Behavior

The :method:`rs.reconfig()` shell method can trigger the current primary
to step down in some situations. When the
primary steps down, it forceably closes all client connections. This is
primary steps down, it forcibly closes all client connections. This is
by design. Since it may take a period of time to elect a new primary,
schedule reconfiguration changes during maintenance periods to minimize loss of write availability.

Expand Down
2 changes: 1 addition & 1 deletion source/tutorial/rotate-log-files.txt
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ rather than writing it to a file.
Forcing a Log Rotation with ``SIGUSR1``
---------------------------------------

For Linux and Unix-based systems, you can use the ``SIGURS1`` signal
For Linux and Unix-based systems, you can use the ``SIGUSR1`` signal
to rotate the logs for a single process, as in the following:

.. code-block:: sh
Expand Down