some doc corrections (#394)

_docs/concepts/traffic-management/rules-configuration.md

@@ -319,9 +319,11 @@ the "reviews" microservice.
 
 ```yaml
 destination: reviews.default.svc.cluster.local
-tags:
+policy:
+- tags:
     version: v1
-loadBalancing: RANDOM
+  loadBalancing:
+    name: RANDOM
 ```
 
 ### Circuit breakers
@@ -333,7 +335,8 @@ sets a limit of 100 connections to "reviews" service version "v1" backends.
 
 ```yaml
 destination: reviews.default.svc.cluster.local
-tags:
+policy:
+- tags:
     version: v1
   circuitBreaker:
     simpleCb:
@@ -363,7 +366,8 @@ consider the following rule, as the one and only rule defined for the
 
 ```yaml
 destination: reviews.default.svc.cluster.local
-tags:
+policy:
+- tags:
     version: v1
   circuitBreaker:
     simpleCb:
@@ -394,6 +398,5 @@ Although the default Istio behavior conveniently sends traffic from all
 versions of a source service to all versions of a destination service
 without any rules being set, as soon as version discrimination is desired
 rules are going to be needed.
-
 Therefore, setting a default rule for every service, right from the
 start, is generally considered a best practice in Istio.

_docs/reference/config/traffic-rules/destination-policies.md

@@ -22,8 +22,6 @@ look as follows:
     policy:
     - loadBalancing: 
         name: RANDOM
-      simpleCb:
-        maxConnections: 1000
 
 
 Policies are applicable per individual service versions. ONLY

_posts/2017-06-14-0.1-canary.md

@@ -197,7 +197,7 @@ As before, the autoscalers bound to the 2 version Deployments will automatically
 
 ## Summary
 
-In this article we’ve shown how Istio supports general scalable canary deployments, and how this differs from the basic deployment support in Kubernetes. Istio’s service mesh provides the control necessary to manage traffic distribution with complete independence from deployment scaling. This allows for a simpler, yet significantly more functional, way to do canary test and rolloout. 
+In this article we’ve shown how Istio supports general scalable canary deployments, and how this differs from the basic deployment support in Kubernetes. Istio’s service mesh provides the control necessary to manage traffic distribution with complete independence from deployment scaling. This allows for a simpler, yet significantly more functional, way to do canary test and rollout. 
 
 Intelligent routing in support of canary deployment is just one of the many features of Istio that will make the production deployment of large-scale microservices-based applications much simpler. Check out [istio.io]({{home}}) for more information and to try it out.
 The sample code used in this article can be found [here](https://github.com/istio/istio/tree/master/samples/apps/helloworld).