DOCS-471 minor edits

Author: Bob Grabar

source/administration/ulimit.txt

@@ -24,9 +24,9 @@ deployment and its use to determine ideal ``ulimit`` settings.
 Generally, all :program:`mongod` and :program:`mongos` instances, like
 other processes:
 
-- tracks each incoming connection with a file descriptor *and* a thread.
+- track each incoming connection with a file descriptor *and* a thread.
 
-- tracks each internal thread or *pthread* as a system process. 
+- track each internal thread or *pthread* as a system process. 
 
 ``mongod``
 ~~~~~~~~~~
@@ -41,16 +41,16 @@ other processes:
   all other members of the set. 
 
 :program:`mongod` uses background threads for a number of internal
-processes, including :ref:`TTL collections <ttl-collections>` and
-replication, replica set health checks, which may require a small
+processes, including :ref:`TTL collections <ttl-collections>`,
+replication, and replica set health checks, which may require a small
 number of additional resources.
 
 ``mongos``
 ~~~~~~~~~~
 
 In addition to the threads and file descriptors for client
 connections, :program:`mongos` must maintain connects to all config
-servers, and all shards, which includes all members of all replica
+servers and all shards, which includes all members of all replica
 sets.
 
 For :program:`mongos`, consider the following behaviors:
@@ -101,8 +101,8 @@ system limits, as in the following example:
 
 ``ulimit`` refers to the per-*user* limitations for various
 resources. Therefore, if your :program:`mongod` instance executes as a
-user that is also running multiple process, or multiple
-:program:`mongod` process, you might see contention for these
+user that is also running multiple processes, or multiple
+:program:`mongod` processes, you might see contention for these
 resources. Also, be aware that the ``processes`` value (i.e. ``-u``)
 refers to the combined number of distinct processes and sub-process
 threads.