diff --git a/source/reference/command/logRotate.txt b/source/reference/command/logRotate.txt
index 20a689a2195..eda88577894 100644
--- a/source/reference/command/logRotate.txt
+++ b/source/reference/command/logRotate.txt
@@ -43,8 +43,8 @@ logRotate
    .. note::
 
       .. versionadded:: 2.0.3   
-      The :dbcommand:`logRotate` command is available to 
-      :program:`mongod` instances running on Windows systems with 
-      MongoDB release 2.0.3 and higher.
+         The :dbcommand:`logRotate` command is available to 
+         :program:`mongod` instances running on Windows systems with 
+         MongoDB release 2.0.3 and higher.
 
 .. :error:`16175` is thrown if logRotate fails
diff --git a/source/reference/configuration-options.txt b/source/reference/configuration-options.txt
index 6975bdf5b76..eba520aed8c 100644
--- a/source/reference/configuration-options.txt
+++ b/source/reference/configuration-options.txt
@@ -727,7 +727,7 @@ Sharding Cluster Options
 
    *Default:* false
 
-   When set to ``true``, :setting:``noMoveParanoia` disables a
+   When set to ``true``, :setting:`noMoveParanoia` disables a
    "paranoid mode" for data writes for chunk migration operation. See
    the :ref:`chunk migration <sharding-chunk-migration>` and
    :dbcommand:`moveChunk` command documentation for more information.
diff --git a/source/replication.txt b/source/replication.txt
index 842a8bf441f..e4b33043c5e 100644
--- a/source/replication.txt
+++ b/source/replication.txt
@@ -42,10 +42,10 @@ operations in detail:
    :maxdepth: 1
 
    tutorial/deploy-replica-set
+   tutorial/convert-standalone-to-replica-set
    tutorial/expand-replica-set
    tutorial/deploy-geographically-distributed-replica-set
    tutorial/change-oplog-size
-   tutorial/convert-replica-set-to-replicated-shard-cluster
    tutorial/change-hostnames-in-a-replica-set
    tutorial/convert-secondary-into-arbiter
 
diff --git a/source/sharding.txt b/source/sharding.txt
index f355b9240c6..3d0af73fd45 100644
--- a/source/sharding.txt
+++ b/source/sharding.txt
@@ -49,6 +49,7 @@ The following tutorials describe specific sharding procedures:
    tutorial/add-shards-to-shard-cluster
    tutorial/remove-shards-from-cluster
    tutorial/enforce-unique-keys-for-sharded-collections
+   tutorial/convert-replica-set-to-replicated-shard-cluster
 
 .. _sharding-reference:
 
diff --git a/source/tutorial/convert-standalone-to-replica-set.txt b/source/tutorial/convert-standalone-to-replica-set.txt
new file mode 100644
index 00000000000..bc6e4be4746
--- /dev/null
+++ b/source/tutorial/convert-standalone-to-replica-set.txt
@@ -0,0 +1,64 @@
+=========================================
+Deploy a Replica Set From a Single Server
+=========================================
+
+.. default-domain:: mongodb
+
+This tutorial describes how to deploy a three-member :term:`replica set`
+from a standalone instance of MongoDB.
+
+To deploy a replica set from multiple existing instances of MongoDB, see
+:doc:`/tutorial/deploy-replica-set`.
+
+For background information on replica set deployments, see
+:doc:`/core/replication` and
+:doc:`/administration/replication-architectures`.
+
+Procedure
+---------
+
+These procedures assume you have a standalone instance of MongoDB
+installed. If you have not already installed MongoDB, see the
+:ref:`installation tutorials <tutorials-installation>`.
+
+1. Shut down the your MongoDB instance and then restart using
+   the :option:`--replSet <mongod --replset>` option and the name of the
+   :term:`replica set`, which is ``rs0`` in the example below.
+
+   To minimize downtime, consider pre-allocating new local data files by
+   using the :setting:`oplogSize` option. If you choose not to use this
+   option, the server allocate the new data files before starting back
+   up. This example does not use the :setting:`oplogSize` option.
+
+   Use a command similar to the following:
+
+   .. code-block:: sh
+
+      mongod --port 27017 --replSet rs0
+
+   This starts the instance as a member of a replica set named ``rs0``.
+   For more information on configuration options, see
+   :doc:`/reference/configuration-options`.
+
+#. Open a :program:`mongo` shell and connect to the :program:`mongod`
+   instance. If you are running the command remotely, replace
+   "localhost" with the appropriate hostname. In a new shell session,
+   enter the following:
+
+   .. code-block:: sh
+
+      mongo localhost:27017
+
+#. Use :method:`rs.initiate()` to initiate the replica set:
+
+   .. code-block:: javascript
+
+      rs.initiate()
+
+   The server is now operational as the :term:`primary` in a replica set
+   that consists of a single node. To display the replica configuration,
+   issue the :method:`rs.conf()` method. To check the status of the
+   replica set, issue :method:`rs.status()`.
+
+#. The next step is to add members to the replica set. To do so, see
+   :doc:`/tutorial/expand-replica-set`.
diff --git a/source/tutorial/deploy-replica-set.txt b/source/tutorial/deploy-replica-set.txt
index 3fa2b993042..b4a8bba958b 100644
--- a/source/tutorial/deploy-replica-set.txt
+++ b/source/tutorial/deploy-replica-set.txt
@@ -4,12 +4,17 @@ Deploy a Replica Set
 
 .. default-domain:: mongodb
 
-This tutorial describes how to deploy a three member
-:term:`replica set`, with specific instructions for development
-and test systems and for production systems.
+This tutorial describes how to create a three member
+:term:`replica set` from three existing instances of MongoDB.
+The tutorial provides one procedure for development and test systems and
+a separate procedure for production systems.
 
-.. seealso:: For appropriate background, see :doc:`/core/replication`
-   and :doc:`/administration/replication-architectures`.
+To deploy a replica set from a single standalone MongoDB instance, see
+:doc:`/tutorial/convert-standalone-to-replica-set`.
+
+For background information on replica set deployments, see
+:doc:`/core/replication` and
+:doc:`/administration/replication-architectures`.
 
 Overview
 --------