From 492a88f01d55837e08631e174d597d5d0476e735 Mon Sep 17 00:00:00 2001 From: Xianglin Gao Date: Thu, 11 Aug 2016 11:14:09 +0800 Subject: [PATCH] fix mistakes in api changes Signed-off-by: Xianglin Gao --- docs/devel/api_changes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/devel/api_changes.md b/docs/devel/api_changes.md index c1ce556349e..cd19c55dac8 100755 --- a/docs/devel/api_changes.md +++ b/docs/devel/api_changes.md @@ -493,7 +493,7 @@ hack/update-generated-protobuf.sh The vast majority of objects will not need any consideration when converting to protobuf, but be aware that if you depend on a Golang type in the standard -library there may be additional work requried, although in practice we typically +library there may be additional work required, although in practice we typically use our own equivalents for JSON serialization. The `pkg/api/serialization_test.go` will verify that your protobuf serialization preserves all fields - be sure to run it several times to ensure there are no incompletely calculated fields. @@ -752,7 +752,7 @@ The latter requires that all objects in the same API group as `Frobber` to be replicated in the new version, `v6alpha2`. This also requires user to use a new client which uses the other version. Therefore, this is not a preferred option. -A releated issue is how a cluster manager can roll back from a new version +A related issue is how a cluster manager can roll back from a new version with a new feature, that is already being used by users. See https://github.com/kubernetes/kubernetes/issues/4855.