Minor corrections.

matrix/synapse/workers.md

@@ -109,7 +109,7 @@ sure nginx can write to them: add user `www-data` to group `matrix-synapse`
 and restart nginx.
 
 Then, make sure systemd creates the directory for the sockets as soon as
-Synapse starts, and let it have the correct group.
+Synapse starts:
 
 ```
 systemctl edit matrix-synapse
@@ -144,7 +144,7 @@ listeners:
         - consent
         - federation
 
-  - path: /run/matrix-synapse/replication.sock
+  - path: /run/matrix-synapse/replication_main.sock
     mode: 0660
     type: http
     resources:
@@ -154,7 +154,7 @@ listeners:
 
 This means Synapse will create two sockets under `/run/matrix-synapse`: one
 for incoming traffic that is forwarded by nginx (`inbound_main.sock`), and one for
-communicating with all the other workers (`replication.sock`).
+communicating with all the other workers (`replication_main.sock`).
 
 If you restart Synapse now, it won't do anything anymore, because nginx is
 still forwarding its traffic to `localhost:8008`. We'll get to nginx later,
@@ -214,7 +214,7 @@ We'll create the following workers:
 * accountdata
 * presence
 * receipts
-* initial_sync: 1, 2, 3 and 4
+* initial_sync: 1 and 2
 * normal_sync: 1, 2 and 3
 
 Some of them are `stream_writers`, and the [documentation about