Replace special quote characters with normal ones.

content/en/docs/concepts/architecture/controller.md

@@ -113,9 +113,9 @@ useful changes, it doesn't matter if the overall state is or is not stable.
 As a tenet of its design, Kubernetes uses lots of controllers that each manage
 a particular aspect of cluster state. Most commonly, a particular control loop
 (controller) uses one kind of resource as its desired state, and has a different
-kind of resource that it manages to make that desired state happen. For example, 
+kind of resource that it manages to make that desired state happen. For example,
 a controller for Jobs tracks Job objects (to discover new work) and Pod objects
-(to run the Jobs, and then to see when the work is finished). In this case 
+(to run the Jobs, and then to see when the work is finished). In this case
 something else creates the Jobs, whereas the Job controller creates Pods.
 
 It's useful to have simple controllers rather than one, monolithic set of control
@@ -140,7 +140,7 @@ the {{< glossary_tooltip term_id="kube-controller-manager" >}}. These
 built-in controllers provide important core behaviors.
 
 The Deployment controller and Job controller are examples of controllers that
-come as part of Kubernetes itself (“built-in” controllers).
+come as part of Kubernetes itself ("built-in" controllers).
 Kubernetes lets you run a resilient control plane, so that if any of the built-in
 controllers were to fail, another part of the control plane will take over the work.