docs(readme): Kubernetes example wording

README.md

@@ -165,7 +165,7 @@ Also, see [templating](#templating) and [example](#examples) sections.
   apiVersion: apps/v1
   kind: Deployment
   metadata:
-    name: nginx-deployment
+    name: nginx
   spec:
     selector:
       matchLabels:
@@ -184,7 +184,7 @@ Also, see [templating](#templating) and [example](#examples) sections.
 
   Notice the yaml comment on the same line as `image`.
 
-  If this file was called `nginx.yaml`, then we could replace the image tag by running:
+  If this file was called `nginx.yaml`, then you could replace the image tag by running:
   ```shell
   yampl -i nginx.yaml -v tag=1.21.6
   ```
@@ -194,7 +194,7 @@ Also, see [templating](#templating) and [example](#examples) sections.
   apiVersion: apps/v1
   kind: Deployment
   metadata:
-    name: nginx-deployment
+    name: nginx
   spec:
     selector:
       matchLabels:
@@ -211,13 +211,13 @@ Also, see [templating](#templating) and [example](#examples) sections.
               - containerPort: 80
   ```
 
-  If I wanted to repeat myself even less, I could utilize the `repo` function to pull the existing repo through.
-  I could define the `image` template as:
+  If you wanted to repeat yourself even less, you could use the [`repo`](#repo) function to pull the existing repo through to the output.
+  For example, you could change the `image` line to:
   ```yaml
   image: nginx:1.21.6 #yampl {{ repo current }}:{{ .tag }}
   ```
 
-  This would generate the same output, but I didn't have to type `nginx` twice.
+  This would generate the same output, but you wouldn't have to type `nginx` twice.
   This becomes more useful when using custom Docker registries where repo names can get long.
 
 </details>