README.md in einhorn-0.4.3 vs README.md in einhorn-0.4.4

@@ -79,19 +79,19 @@
 
     ADDR := (IP:PORT)[<,OPT>...]
 
 In the worker process, the opened file descriptors will be represented
 as file descriptor numbers in a series of environment variables named
-EINHORN_FD_1, EINHORN_FD_2, etc. (respecting the order that the `-b`
+EINHORN_FD_0, EINHORN_FD_1, etc. (respecting the order that the `-b`
 options were provided in), with the total number of file descriptors
 in the EINHORN_FD_COUNT environment variable:
 
-    EINHORN_FD_1="6" # 127.0.0.1:1234
+    EINHORN_FD_0="6" # 127.0.0.1:1234
     EINHORN_FD_COUNT="1"
 
-    EINHORN_FD_1="6" # 127.0.0.1:1234,r
-    EINHORN_FD_2="7" # 127.0.0.1:1235
+    EINHORN_FD_0="6" # 127.0.0.1:1234,r
+    EINHORN_FD_1="7" # 127.0.0.1:1235
     EINHORN_FD_COUNT="2"
 
 Valid opts are:
 
     r, so_reuseaddr: set SO_REUSEADDR on the server socket
@@ -101,10 +101,10 @@
 
     $ einhorn -b 127.0.0.1:2345,r -m manual -n 4 -- example/time_server
 
 Which will run 4 copies of
 
-    EINHORN_FD_1=6 EINHORN_FD_COUNT=1 example/time_server
+    EINHORN_FD_0=6 EINHORN_FD_COUNT=1 example/time_server
 
 Where file descriptor 6 is a server socket bound to `127.0.0.1:2345`
 and with `SO_REUSEADDR` set. It is then your application's job to
 figure out how to `accept()` on this file descriptor.