modification to reflect CONN_LIMIT only for Kubernetes

site/concepts/network-topology.md

@@ -142,13 +142,15 @@ is not reachable, then the packet is dropped.  For most protocols
 (for example, TCP), the transmission will be retried a short time later, by
 which time the topology should have updated.
 
-#### connection limit
+#### <a name="connection-limit"></a>Connection Limit
 
 In a fully connected mesh of N peers, this would mean N^2 connections. To constrain the resource consumption and 
 communication between the peers and complexity of route calculation there is a configurable upper limit on the 
 maximum number of connections that a peer can make to the remote peers. There is safe default value (100) which works
 for most deployment. However if you would like to increase the number of peers, you should be able to explicitly override the
-default value by setting the CONN_LIMIT environment variable or explicitly invoking weave launch like `weave launch --connlimit=100`.
+default value by passing the value through `connlimit` flag for e.g.`weave launch --connlimit=100`. If you are using Weave with
+Kubernetes using [Kubernetes Addon](/site/kubernetes/kube-addon.md) then you can set CONN_LIMIT environment variable to set
+the connection limit.
 
 **See Also**