website: fix proxies to work via copy/paste

website/source/docs/connect/proxies.html.md

@@ -63,9 +63,12 @@ default managed proxy and starts a listener for that service:
 
 ```json
 {
-  "service": "redis",
+  "service": {
+    "name": "redis",
+    "port": 6379,
     "connect": { "proxy": {} }
   }
+}
 ```
 
 The listener is started on random port within the configured Connect
@@ -85,7 +88,9 @@ proxy configuration:
 
 ```json
 {
-  "service": "web",
+  "service": {
+    "name": "web",
+    "port": 8080,
     "connect": {
       "proxy": {
         "config": {
@@ -97,6 +102,7 @@ proxy configuration:
       }
     }
   }
+}
 ```
 
 In the example above,
@@ -125,12 +131,14 @@ service.
 
 ```json
 {
-  "service": "web",
+  "service": {
+    "name": "web",
+    "port": 8080,
     "connect": {
       "proxy": {
         "config": {
           "upstreams": [{
-            "destination_name": "nearest-redis",
+              "destination_name": "redis",
               "destination_type": "prepared_query",
               "local_bind_port": 1234
           }]
@@ -138,6 +146,7 @@ service.
       }
     }
   }
+}
 ```
 
 -> **Note:** Connect does not currently support cross-datacenter
@@ -160,9 +169,11 @@ can be used.
 configured to run as a managed proxy. To configure custom proxies, specify
 an alternate command to execute for the proxy:
 
-```
+```json
 {
-  "service": "web",
+  "service": {
+    "name": "web",
+    "port": 8080,
     "connect": {
       "proxy": {
         "exec_mode": "daemon",
@@ -170,6 +181,7 @@ an alternate command to execute for the proxy:
       }
     }
   }
+}
 ```
 
 The `exec_mode` value specifies how the proxy is executed. The only