Fix broken link by removing invalid characters.... (#1605)

* Fix broken link by removing invalid characters....

The link to this page is broken because of invalid characters introduced with PR #1549.

* Update networking.md

docs/admin/networking.md

@@ -83,7 +83,7 @@ talk to other VMs in your project.  This is the same basic model.
 Until now this document has talked about containers.  In reality, Kubernetes
 applies IP addresses at the `Pod` scope - containers within a `Pod` share their
 network namespaces - including their IP address.  This means that containers
-within a `Pod` can all reach each other’s ports on `localhost`.  This does imply
+within a `Pod` can all reach each other's ports on `localhost`. This does imply 
 that containers within a `Pod` must coordinate port usage, but this is no
 different than processes in a VM.  We call this the "IP-per-pod" model.  This
 is implemented in Docker as a "pod container" which holds the network namespace
@@ -163,7 +163,7 @@ Lars Kellogg-Stedman.
 [Weave Net](https://www.weave.works/products/weave-net/) is a 
 resilient and simple to use network for Kubernetes and its hosted applications.  
 Weave Net runs as a [CNI plug-in](https://www.weave.works/docs/net/latest/cni-plugin/)  
-or stand-alone.  In either version, it doesn’t require any configuration or extra code 
+or stand-alone.  In either version, it doesn't require any configuration or extra code
 to run, and in both cases, the network provides one IP address per pod - as is standard for Kubernetes.