add verbatim copy of config

README.md

@@ -35,7 +35,35 @@ Currently its location is fixed as all my deployments are for a single network.
 I may add a feature to allow setting of the location via environment variable
 in the future to support multiple networks on a single host.
 
-Main configuration, generated by `dsnet init` and edited manually:
+Main configuration example, generated by `dsnet init` and edited manually:
+
+
+    {
+        "ExternalIP": "198.51.100.2",
+        "ListenPort": 51820,
+        "Domain": "dsnet",
+        "InterfaceName": "dsnet",
+        "Network": "10.164.236.0/22",
+        "IP": "10.164.236.1",
+        "DNS": "",
+        "Networks": [],
+        "ReportFile": "/var/lib/dsnetreport.json",
+        "PrivateKey": "uC+xz3v1mfjWBHepwiCgAmPebZcY+EdhaHAvqX2r7U8=",
+        "Peers": [
+            {
+                "Hostname": "test",
+                "Owner": "naggie",
+                "Description": "Home server",
+                "IP": "10.164.236.2",
+                "Added": "2020-05-07T10:04:46.336286992+01:00",
+                "Networks": [],
+                "PublicKey": "altJeQ/V52JZQrGcA9RiKcpZusYU6zMUJhl7Wbd9rX0=",
+                "PresharedKey": "GcUtlze0BMuxo3iVEjpOahKdTf8xVfF8hDW3Ylw5az0="
+            }
+        ]
+    }
+
+Explanation of each field:
 
     {
         "ExternalIP": "198.51.100.2",
@@ -174,7 +202,7 @@ dsnet after adding peers. I use it in production at 2 companies so far.
 Note that before version 1.0, the config file schema may change. Changes will
 be made clear in release notes.
 
-> Why are their very few issues?
+> Why are there very few issues?
 
 I'm tracking development elsewhere using
 [dstask](https://github.com/naggie/dstask). I keep public initiated issues on