Skip to content

Minor edits for fixing markup. #1315

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.

Sign up for GitHub

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

Minor edits for fixing markup. #1315

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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/release-notes/2.6.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ development series as a work-in-progress.
Downloading
-----------

You can download the current 2.5 development release on the`downloads
You can download the current 2.5 development release on the `downloads
page`_ in the :guilabel:`Development Release (Unstable)`
section. There are no distribution packages for development releases,
but you can use the binaries provided for testing purposes. See
Expand Down
14 changes: 7 additions & 7 deletions source/tutorial/upgrade-revision.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,17 +124,17 @@ To upgrade a sharded cluster:
server is always running. For each config server upgrade, follow the
instructions below in :ref:`upgrade-mongodb-instance`

..example:: Given the following config string:
.. example:: Given the following config string:

.. code-block:: sh
.. code-block:: sh

mongos --configdb cfg0.example.net:27019,cfg1.example.net:27019,cfg2.example.net:27019
mongos --configdb cfg0.example.net:27019,cfg1.example.net:27019,cfg2.example.net:27019

You would upgrade the config servers in the following order:
You would upgrade the config servers in the following order:

1. cfg2.example.net
2. cfg1.example.net
3. cfg0.example.net
1. cfg2.example.net
2. cfg1.example.net
3. cfg0.example.net

#. Upgrade each shard.

Expand Down