Merge pull request #57404 from nikhita/apimachinery-readme-typos

Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

apimachinery: fix typos in README

So that we can close https://github.com/kubernetes/apimachinery/pull/32, https://github.com/kubernetes/apimachinery/pull/27, https://github.com/kubernetes/apimachinery/pull/20.

**Release note**:

```release-note
NONE
```

/assign sttts
This commit is contained in:
Kubernetes Submit Queue 2017-12-19 09:20:16 -08:00 committed by GitHub
commit 386f9dd2e0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -6,7 +6,7 @@ Scheme, typing, encoding, decoding, and conversion packages for Kubernetes and K
## Purpose ## Purpose
This library is a shared dependency for servers and clients to work with Kubernetes API infrastructure without direct This library is a shared dependency for servers and clients to work with Kubernetes API infrastructure without direct
type dependencies. It's first comsumers are `k8s.io/kubernetes`, `k8s.io/client-go`, and `k8s.io/apiserver`. type dependencies. Its first consumers are `k8s.io/kubernetes`, `k8s.io/client-go`, and `k8s.io/apiserver`.
## Compatibility ## Compatibility
@ -25,5 +25,5 @@ Code changes are made in that location, merged into `k8s.io/kubernetes` and late
## Things you should *NOT* do ## Things you should *NOT* do
1. Add API types to this repo. This is for the machinery, not for the types. 1. Add API types to this repo. This is for the machinery, not for the types.
2. Directly modify any files under `pkg` in this repo. Those are driven from `k8s.io/kuberenetes/staging/src/k8s.io/apimachinery`. 2. Directly modify any files under `pkg` in this repo. Those are driven from `k8s.io/kubernetes/staging/src/k8s.io/apimachinery`.
3. Expect compatibility. This repo is direct support of Kubernetes and the API isn't yet stable enough for API guarantees. 3. Expect compatibility. This repo is direct support of Kubernetes and the API isn't yet stable enough for API guarantees.