From 640f5c581306d77c983030abe7c39b1f47bd518a Mon Sep 17 00:00:00 2001 From: Ronald Petty Date: Wed, 28 Dec 2016 17:17:30 -0800 Subject: [PATCH] Update accessing-the-api.md Minor typo fixes. * missing paran * needed space --- docs/admin/accessing-the-api.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/admin/accessing-the-api.md b/docs/admin/accessing-the-api.md index a70f1c0920..92de1772ab 100644 --- a/docs/admin/accessing-the-api.md +++ b/docs/admin/accessing-the-api.md @@ -94,7 +94,7 @@ to restrict what users can do. The Authorization step is designed to operate on attributes that are likely to be common to most REST requests, such as object name, kind, etc. This is intended to facilitate interation with existing organization-wide or cloud-provider-wide access control systems (which may handle -other APIs besides the Kubernetes API. +other APIs besides the Kubernetes API). Access controls and policies that depend on specific fields of specific Kinds of objects are handled by Admission Controllers. @@ -127,7 +127,7 @@ for the corresponding API object, and then written to the object store (shown as The previous discussion applies to requests sent to the secure port of the API server (the typical case). The API server can actually serve on 2 ports: -By default the Kubernetes APIserver serves HTTP on 2 ports: +By default the Kubernetes API server serves HTTP on 2 ports: 1. `Localhost Port`: