Step F-22) of page [b] has unterminated JSON

[byforcesunseen]

The example JSON in Step F-22 of page b is missing a closing bracket. This will cause the following error when using tezos-client run:

./tezos-node run
tezos-node: Error:
              Ezjsonm.Parse_error(870828711, "JSON.of_buffer unclosed
            object")

Incorrect example provided below:

F-22) Modify the tezos file config.json located in ./.tezos-node

These are some of configuration parameters that I found helping to run Tezos better on the RPI3 (still under revision Aug/25). As a user, just create a config.json file and add the following:

{
   "rpc": {
   "listen-addr": "localhost:8733",
   "cors-headers": [
   "content-type"
   ],
   "cors-origin": [
   "*"
   ]
  },
  "p2p": {
   "bootstrap-peers": [
   "boot.tzbeta.net",
   "localhost:7733"
   ],
   "listen-addr": "localhost:9733",
   "limits":{
   "connection-timeout":15,
   "authentication-timeout":10,
   "max-connections":10,
   "expected-connections": 10,
   "max-incoming-connections": 0,
   "backlog": 0,
   "read-buffer-size":16384,
   "read-queue-size":1024,
   "write-queue-size":1024,
   "swap-linger":60,
   "max_known_points":[400,300],
   "max_known_peer_ids":[400,300]}
  },
   "shell":{
   "chain_validator":{"bootstrap_threshold":10}}

The last line in the above example should have another closing bracket:

   "shell":{
     "chain_validator":{"bootstrap_threshold":10}
   }
}

[maxtez-raspbaker]

@byforcesunseen my apologies for the late reply, yes, what you have listed is the correct format. Check out also the latest version of the config.json file. It is better suited for the mainnet at the present time. (please send me an email if I don't reply to any inquire within 1-2 days)