Change .. code:: to .. code-block::

Sphinx uses .. code-block:: directives to enable highlighting:
http://sphinx-doc.org/markup/code.html#directive-code-block

Use

  for i in *.rst; do
        sed -i 's/code::/code-block::/g' $i
    done

to update these strings to enable proper highlighting.

Note: A have disabled the windows "bash" one, because the highlighting
is broken anyway...

events/configsaved.rst

@@ -4,7 +4,7 @@ ConfigSaved
 Emitted after the config has been saved by the user or by Syncthing
 itself.
 
-.. code:: json
+.. code-block:: json
 
     {
         "id": 50,

events/deviceconnected.rst

@@ -3,7 +3,7 @@ DeviceConnected
 
 Generated each time a connection to a device has been established.
 
-.. code:: json
+.. code-block:: json
 
     {
         "id": 2,

events/devicedisconnected.rst

@@ -3,7 +3,7 @@ DeviceDisconnected
 
 Generated each time a connection to a device has been terminated.
 
-.. code:: json
+.. code-block:: json
 
     {
         "id": 48,

events/devicediscovered.rst

@@ -3,7 +3,7 @@ DeviceDiscovered
 
 Emitted when a new device is discovered using local discovery.
 
-.. code:: json
+.. code-block:: json
 
     {
         "id": 13,

events/devicerejected.rst

@@ -4,7 +4,7 @@ DeviceRejected
 Emitted when there is a connection from a device we are not configured
 to talk to.
 
-.. code:: json
+.. code-block:: json
 
     {
         "id": 24,

events/downloadprogress.rst

@@ -5,7 +5,7 @@ Emitted during file downloads for each folder for each file. By default
 only a single file in a folder is handled at the same time, but custom
 configuration can cause multiple files to be shown.
 
-.. code:: json
+.. code-block:: json
 
     {
         "id": 221,

events/foldercompletion.rst

@@ -6,7 +6,7 @@ contents for a folder changes. It contains the completion percentage for
 a given remote device and is emitted once per currently connected remote
 device.
 
-.. code:: json
+.. code-block:: json
 
     {
         "id": 84,

events/folderrejected.rst

@@ -4,7 +4,7 @@ FolderRejected
 Emitted when a device sends index information for a folder we do not
 have, or have but do not share with the device in question.
 
-.. code:: json
+.. code-block:: json
 
     {
         "id": 27,

events/foldersummary.rst

@@ -5,7 +5,7 @@ The FolderSummary event is emitted when folder contents have changed
 locally. This can be used to calculate the current local completion
 state.
 
-.. code:: json
+.. code-block:: json
 
     {
         "id": 16,

events/itemfinished.rst

@@ -4,7 +4,7 @@ ItemFinished
 Generated when Syncthing ends synchronizing a file to a newer version. A
 successful operation:
 
-.. code:: json
+.. code-block:: json
 
     {
         "id": 93,
@@ -21,7 +21,7 @@ successful operation:
 
 An unsuccessful operation:
 
-.. code:: json
+.. code-block:: json
 
     {
         "id": 44,

events/itemstarted.rst

@@ -3,7 +3,7 @@ ItemStarted
 
 Generated when Syncthing begins synchronizing a file to a newer version.
 
-.. code:: json
+.. code-block:: json
 
     {
         "id": 93,

events/localindexupdated.rst

@@ -5,7 +5,7 @@ Generated when the local index information has changed, due to
 synchronizing one or more items from the cluster or discovering local
 changes during a scan.
 
-.. code:: json
+.. code-block:: json
 
     {
         "id": 59,

events/ping.rst

@@ -5,7 +5,7 @@ The Ping event is generated automatically every 60 seconds. This means
 that even in the absence of any other activity, the event polling HTTP
 request will return within a minute.
 
-.. code:: json
+.. code-block:: json
 
     {
         "id": 46,

events/remoteindexupdated.rst

@@ -3,7 +3,7 @@ RemoteIndexUpdated
 
 Generated each time new index information is received from a device.
 
-.. code:: json
+.. code-block:: json
 
     {
         "id": 44,

events/starting.rst

@@ -4,7 +4,7 @@ Starting
 Emitted exactly once, when Syncthing starts, before parsing
 configuration etc.
 
-.. code:: json
+.. code-block:: json
 
     {
         "id": 1,

events/startupcomplete.rst

@@ -4,7 +4,7 @@ StartupCompleted
 Emitted exactly once, when initialization is complete and Syncthing is
 ready to start exchanging data with other devices.
 
-.. code:: json
+.. code-block:: json
 
     {
         "id": 1,

events/statechanged.rst

@@ -7,7 +7,7 @@ the number of seconds the folder spent in state ``from``. In the example
 below, the folder ``default`` was in state ``scanning`` for 0.198
 seconds and is now in state ``idle``.
 
-.. code:: json
+.. code-block:: json
 
     {
         "id": 8,