fix typos

docs/src/snap/explanation/upgrade.md

@@ -58,7 +58,7 @@ revision of the snap it orchestrates, the `refresh` function of the snap has
 been frozen and all upgrades must be done through Juju. The `juju refresh`
 command instructs the Juju controller
 to use the new charm revision within the current charm channel or to upgrade to
-the next channel based on the paramaters provided. The charm code
+the next channel based on the parameters provided. The charm code
 is simultaneously replaced on each unit. Then, the k8s snap is updated
 unit-by-unit. This is in order to maintain a highly-available kube-api-server
 endpoint, starting with the Juju leader unit for the application. To ensure a
@@ -75,7 +75,7 @@ on [upgrading your cluster by a minor version].
 
 High availability is automatically enabled in {{ product }} for clusters with
 three or more nodes independent of the deployment method. Clusters without high
-availability must be extra viligant on backing up cluster data before starting
+availability must be extra vigilant on backing up cluster data before starting
 the upgrade process and also must be aware of potential service disruptions
 during cluster upgades. It is also important to understand that Kubernetes will
 only upgrade and if necessary migrate, components relating specifically to