Fix syntax in examples of 'duniter sync'

content/pages/wiki/duniter/commands.md

@@ -47,7 +47,7 @@ For a new or deleted node (for example, following the use of `reset data`), it i
 
 Synchronize its node with the network Ğ1 (Duniter currency):
 
-    duniter sync g1.duniter.org 443
+    duniter sync g1.duniter.org:443
     Progress:
 
     download: [|||| ] 23%
@@ -59,7 +59,7 @@ This command takes time. Be patient.
 
 Disables the display with progress bars in favor of a conventional control output.
 
-    duniter sync g1.duniter.org 443
+    duniter sync g1.duniter.org:443
     2017-04-10T08: 31: 42 + 02: 00 - info: Try with g1.duniter.org:10901 4aCqwi
     2017-04-10T08: 31: 42 + 02: 00 - info: Sync started.
     2017-04-10T08: 31: 42 + 02: 00 - info: Getting remote blockchain info ...
@@ -70,7 +70,7 @@ Disables the display with progress bars in favor of a conventional control outpu
 
 Disables P2P downloading and downloading of network node listing.
 
-    duniter sync g1.duniter.org 443
+    duniter sync g1.duniter.org:443
     2017-04-10T08: 32: 26 + 02: 00 - info: Try with g1.duniter.org:10901 4aCqwi
     2017-04-10T08: 32: 26 + 02: 00 - info: Sync started.
     2017-04-10T08: 32: 26 + 02: 00 - info: Getting remote blockchain info ...
@@ -88,13 +88,13 @@ Retrieves only peer information, does not retrieve block information.
 
 Force the careful verification of the validity of each block in relation to the rules of the protocol.
 
-    duniter sync g1.duniter.org 443 --cautious
+    duniter sync g1.duniter.org:443 --cautious
 
 #### Option `--memory`
 
 Perform synchronization in memory only. Synchronization will not be stored on the hard disk. This option is useful for a quick blockchain integrity check when combined with the `--cautious` option.
 
-    duniter sync g1.duniter.org 443 --cautious --memory
+    duniter sync g1.duniter.org:443 --cautious --memory
 
 ## Start / Stop its node
 
@@ -363,7 +363,7 @@ Because these options allow you to temporarily reset (the time of a command) a g
 
 Allows you to redefine the folder where the application data is stored. The default value for this option is `$HOME/.config/duniter/`
 
-    duniter sync g1.duniter.org 10901 --home / tmp / duniter
+    duniter sync g1.duniter.org:10901 --home / tmp / duniter
     
 This command will synchronize and store the result in the `/tmp/duniter/duniter_default` folder.
 
@@ -371,13 +371,13 @@ This command will synchronize and store the result in the `/tmp/duniter/duniter_
 
 Allows you to redefine the folder where the application data is stored. The default value for this option is `duniter_default`.
 
-    duniter sync g1.duniter.org 10901 --mdb g-one
+    duniter sync g1.duniter.org:10901 --mdb g-one
     
 This command will synchronize and store the result in the `$HOME/.config/duniter/g-one` folder.
 
 It is possible to combine the 2 options:
 
-    duniter sync g1.duniter.org 10901 --home / tmp / duniter --mdb g-one
+    duniter sync g1.duniter.org:10901 --home / tmp / duniter --mdb g-one
     
 This command will synchronize and store the result in the `/tmp/duniter/g-one` folder.
 

content/pages/wiki/duniter/install.md

@@ -150,7 +150,7 @@ Without any other option, the container will automatically execute `duniter dire
 
 Once the node is started, it is accessable either using web UI, going to http://localhost:9220, either using command line:
 
-    docker exec -it duniter duniter sync g1.duniter.fr 443
+    docker exec -it duniter duniter sync g1.duniter.fr:443
 
 In the above command, the first `duniter` is the name given to the container at creation time, while the second one is the executed command.