chore: fix small typo in documentation

Signed-off-by: ductnn <trannhuduc531998@gmail.com>

Author: ductnn

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

@@ -65,7 +65,7 @@ apiserver-1dfef752bcb36637d2763d1868 apiserver-1dfef752bcb36637d2763d1868
 The SHA256 hash used in the lease name is based on the OS hostname as seen by that API server. Each kube-apiserver should be
 configured to use a hostname that is unique within the cluster. New instances of kube-apiserver that use the same hostname
 will take over existing Leases using a new holder identity, as opposed to instantiating new Lease objects. You can check the
-hostname used by kube-apisever by checking the value of the `kubernetes.io/hostname` label:
+hostname used by kube-apiserver by checking the value of the `kubernetes.io/hostname` label:
 
 ```shell
 kubectl -n kube-system get lease apiserver-07a5ea9b9b072c4a5f3d1c3702 -o yaml

content/en/docs/concepts/cluster-administration/flow-control.md

@@ -95,7 +95,7 @@ way to do that is with the objects that configure classification and
 handling, discussed below. Another way is to disable Priority and
 Fairness on server B entirely, using the techniques discussed above. A
 third way, which is the simplest to use when server B is not
-`kube-apisever`, is to build server B with Priority and Fairness
+`kube-apiserver`, is to build server B with Priority and Fairness
 disabled in the code.
 
 ## Concepts