minor edits

docs/user-journeys/users/application-developer/advanced.md

@@ -11,7 +11,7 @@ track: "USERS › APPLICATION DEVELOPER › ADVANCED"
 {% capture overview %}
 
 {: .note }
-This page assumes that you're familiar with core Kubernetes concepts, and are comfortable deploying your own apps. If not, we recommend reviewing the [Intermediate App Developer](/docs/user-journeys/users/application-developer/intermediate/){:target="_blank"} topics first.
+This page assumes that you're familiar with core Kubernetes concepts, and are comfortable deploying your own apps. If not, you should review the [Intermediate App Developer](/docs/user-journeys/users/application-developer/intermediate/){:target="_blank"} topics first.
 
 After checking out the current page and its linked sections, you should have a better understanding of the following:
 * Advanced features that you can leverage in your application
@@ -44,10 +44,10 @@ Below are some other, lesser-known ways of configuring your resources' Pods:
 
 #### Additional API Objects
 
-* **{% glossary_tooltip text="Horizontal Pod Autoscaler (HPA)" term_id="horizontal-pod-autoscaler" %}** - These resources are a great way to automate the process of scaling your application when CPU usage or other [custom metrics](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/instrumentation/custom-metrics-api.md){:target="_blank"} spike. [See an example](/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/){:target="_blank"} to understand how HPAs are set up.
+{: .note }
+Before setting up the following resources, check to see if they are the responsibility of your organization's {% glossary_tooltip text="cluster operators" term_id="cluster-operator" %}.
 
-  {: .note }
-  Before setting up an HPA, check to see if this task is the responsibility of your organization's {% glossary_tooltip text="cluster operators" term_id="cluster-operator" %}
+* **{% glossary_tooltip text="Horizontal Pod Autoscaler (HPA)" term_id="horizontal-pod-autoscaler" %}** - These resources are a great way to automate the process of scaling your application when CPU usage or other [custom metrics](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/instrumentation/custom-metrics-api.md){:target="_blank"} spike. [See an example](/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/){:target="_blank"} to understand how HPAs are set up.
 
 * **Federated cluster objects** - If you are running an application on multiple Kubernetes clusters using *federation*, you need to deploy the federated version of the standard Kubernetes API objects. For reference, check out the guides for setting up [Federated ConfigMaps](/docs/tasks/administer-federation/configmap/){:target="_blank"} and [Federated Deployments](/docs/tasks/administer-federation/deployment/){:target="_blank"}.
 
@@ -103,7 +103,7 @@ If you do not have a {% glossary_tooltip text="cluster operator" term_id="cluste
 
 The following topics are also useful for building more complex applications:
 * [Other points of extensibility within Kubernetes](/docs/concepts/overview/extending/){:target="_blank"} -  A conceptual overview of where you can hook into the Kubernetes architecture.
-* [Kubernetes Client Libraries](/docs/reference/client-libraries/){:target="_blank"} - Useful for building apps that need to interact with the Kubernetes API.
+* [Kubernetes Client Libraries](/docs/reference/client-libraries/){:target="_blank"} - Useful for building apps that need to interact heavily with the Kubernetes API.
 
 #### What's next
 Congrats on completing the Application Developer user journey! You've covered the majority of features that Kubernetes has to offer. What now?

docs/user-journeys/users/application-developer/foundational.md

@@ -12,7 +12,7 @@ track: "USERS › APPLICATION DEVELOPER › FOUNDATIONAL"
 If you're a developer looking to run applications on Kubernetes, this page and its linked topics can help you get started with the fundamentals. Though this page primarily describes development workflows, [the subsequent page in the series](/docs/home/?path=users&persona=app-developer&level=intermediate){:target="_blank"} cover more advanced, production setups.
 
 {: .note }
-**A quick note**<br>Generally, app developers can focus more on *what* they're deploying to Kubernetes, rather than *how* the underlying infrastructure works. Though it's possible for a single person to manage both, in many organizations, it’s common to assign the latter to a dedicated {% glossary_tooltip text="cluster operator" term_id="cluster-operator" %}. The cluster operator takes on the responsibility of setting up and maintaining Kubernetes clusters.<br><br>As a result, the app developer "user journey" is *not* a comprehensive overview of Kubernetes. It does, however, highlight the aspects of cluster operation that are relevant to development, testing, and deployment of applications.
+**A quick note**<br>This app developer "user journey" is *not* a comprehensive overview of Kubernetes. It focuses more on *what* you develop, test, and deploy to Kubernetes, rather than *how* the underlying infrastructure works.<br><br>Though it's possible for a single person to manage both, in many organizations, it’s common to assign the latter to a dedicated {% glossary_tooltip text="cluster operator" term_id="cluster-operator" %}.
 
 {% endcapture %}
 

docs/user-journeys/users/application-developer/intermediate.md

@@ -12,7 +12,7 @@ track: "USERS › APPLICATION DEVELOPER › INTERMEDIATE"
 {% capture overview %}
 
 {: .note }
-  This page assumes that you've experimented with Kubernetes before. At this point, you should have basic experience interacting with a Kubernetes cluster (locally with Minikube, or elsewhere), and using API objects like Deployments to run your applications.<br><br>If not, we recommend reviewing the [Beginner App Developer](/docs/user-journeys/users/application-developer/foundational/){:target="_blank"} topics first.
+  This page assumes that you've experimented with Kubernetes before. At this point, you should have basic experience interacting with a Kubernetes cluster (locally with Minikube, or elsewhere), and using API objects like Deployments to run your applications.<br><br>If not, you should review the [Beginner App Developer](/docs/user-journeys/users/application-developer/foundational/){:target="_blank"} topics first.
 
 After checking out the current page and its linked sections, you should have a better understanding of the following:
 * Additional Kubernetes workload patterns, beyond Deployments
@@ -68,11 +68,11 @@ In contrast to Deployments, these API objects are finite. They stop once the spe
 
 For more info, you can check out [a list of additional Kubernetes resource types](/docs/reference/kubectl/overview/#resource-types){:target="_blank"} as well as the [API reference docs]({{ reference_docs_url }}){:target="_blank"}.
 
-There may be additional features not mentioned here that you may find useful. For that, we recommend searching or browsing through the [full Kubernetes documentation](/docs/home/#browsedocs){:target="_blank"}.
+There may be additional features not mentioned here that you may find useful, which are covered in the [full Kubernetes documentation](/docs/home/?path=browse){:target="_blank"}.
 
 ## Deploy a production-ready workload
 
-The beginner tutorials on this sitem such as the [Guestbook app](/docs/tutorials/stateless-application/guestbook/){:target="_blank"}, are geared towards getting workloads up and running on your cluster. This prototyping is great for building your intuition around Kubernetes! However, in order to reliably and securely promote your workloads to production, you'll need to follow some additional best practices.
+The beginner tutorials on this site, such as the [Guestbook app](/docs/tutorials/stateless-application/guestbook/){:target="_blank"}, are geared towards getting workloads up and running on your cluster. This prototyping is great for building your intuition around Kubernetes! However, in order to reliably and securely promote your workloads to production, you'll need to follow some additional best practices.
 
 #### Declarative configuration