Edited 510_Deployment/60_file_descriptors.asciidoc with Atlas code editor

Author: skalapurakkel

510_Deployment/60_file_descriptors.asciidoc

@@ -5,7 +5,7 @@ Lucene uses a _very_ large number of files. ((("deployment", "file descriptors a
 uses a large number of sockets to communicate between nodes and HTTP clients.
 All of this requires available file descriptors.((("file descriptors")))
 
-Sadly, many modern linux distributions ship with a paltry 1024 file descriptors
+Sadly, many modern Linux distributions ship with a paltry 1,024 file descriptors
 allowed per process.  This is _far_ too low for even a small Elasticsearch
 node, let alone one that is handling hundreds of indices.
 
@@ -15,7 +15,7 @@ particular OS and distribution.  Consult the documentation for your OS to determ
 how best to change the allowed file descriptor count.
 
 Once you think you've changed it, check Elasticsearch to make sure it really does
-have enough file descriptors.  You can check with:
+have enough file descriptors:
 
 [source,js]
 ----
@@ -42,19 +42,19 @@ GET /_nodes/process
    }
 }
 ----
-<1> The `max_file_descriptors` field will inform you how many available descriptors
-the Elasticsearch process can access
+<1> The `max_file_descriptors` field shows the number of available descriptors that
+the Elasticsearch process can access.
 
 Elasticsearch also uses a mix of NioFS and MMapFS ((("MMapFS")))for the various files.  Ensure
-that the maximum map count so that there is ample virtual memory available for 
-mmapped files.  This can be set temporarily with:
+that you configure the maximum map count so that there is ample virtual memory available for 
+mmapped files.  This can be set temporarily:
 
 [source,js]
 ----
 sysctl -w vm.max_map_count=262144
 ----
 
-Or permanently by modifying `vm.max_map_count` setting in your `/etc/sysctl.conf`
+Or you can set it permanently by modifying `vm.max_map_count` setting in your `/etc/sysctl.conf`.