fix a series errors of using "a" and "an"

docs/user-guide/connecting-applications.md

@@ -181,7 +181,7 @@ default-token-il9rc   kubernetes.io/service-account-token   1
 nginxsecret           Opaque                                2
 ```
 
-Now modify your nginx replicas to start a https server using the certificate in the secret, and the Service, to expose both ports (80 and 443):
+Now modify your nginx replicas to start an https server using the certificate in the secret, and the Service, to expose both ports (80 and 443):
 
 {% include code.html language="yaml" file="nginx-secure-app.yaml" ghlink="/docs/user-guide/nginx-secure-app" %}
 

docs/user-guide/jobs/work-queue-2/rediswq.py

@@ -95,7 +95,7 @@ class RedisWQ(object):
             # Record that we (this session id) are working on a key.  Expire that
             # note after the lease timeout.
             # Note: if we crash at this line of the program, then GC will see no lease
-            # for this item an later return it to the main queue.
+            # for this item a later return it to the main queue.
             itemkey = self._itemkey(item)
             self._db.setex(self._lease_key_prefix + itemkey, lease_secs, self._session)
         return item

docs/user-guide/load-balancer.md

@@ -93,7 +93,7 @@ Due to the implementation of this feature, the source IP for sessions as seen in
 that will preserve the client Source IP for GCE/GKE environments. This feature will be phased in for other cloud providers in subsequent releases.
 
 ## Annotation to modify the LoadBalancer behavior for preservation of Source IP
-In 1.5, an Beta feature has been added that changes the behavior of the external LoadBalancer feature.
+In 1.5, a Beta feature has been added that changes the behavior of the external LoadBalancer feature.
 
 This feature can be activated by adding the beta annotation below to the metadata section of the Service Configuration file.
 

docs/user-guide/petset.md

@@ -88,7 +88,7 @@ Only use PetSet if your application requires some or all of these properties. Ma
 
 Example workloads for PetSet:
 
-* Databases like MySQL or PostgreSQL that require a single instance attached to a NFS persistent volume at any time
+* Databases like MySQL or PostgreSQL that require a single instance attached to an NFS persistent volume at any time
 * Clustered software like Zookeeper, Etcd, or Elasticsearch that require stable membership.
 
 ## Alpha limitations

docs/user-guide/pods/init-container.md

@@ -105,7 +105,7 @@ If the pod is [restarted](#pod-restart-reasons) all init containers must
 execute again.
 
 Changes to the init container spec are limited to the container image field.
-Altering a init container image field is equivalent to restarting the pod.
+Altering an init container image field is equivalent to restarting the pod.
 
 Because init containers can be restarted, retried, or reexecuted, init container
 code should be idempotent.  In particular, code that writes to files on EmptyDirs