summaryrefslogtreecommitdiff
path: root/contributors/devel/api_changes.md
diff options
context:
space:
mode:
authorsupereagle <jmyue@hotmail.com>2017-02-24 14:26:42 +0800
committersupereagle <jmyue@hotmail.com>2017-02-24 14:26:42 +0800
commit2d53ed8ddb6045fa64eb17091278421c3413bee9 (patch)
tree68e49b94a332398f3ceca9ea19304b60ca7c8116 /contributors/devel/api_changes.md
parent5e45df8618fb02f22538533cd136d9dab5e1f238 (diff)
correct user guide url
Diffstat (limited to 'contributors/devel/api_changes.md')
-rwxr-xr-xcontributors/devel/api_changes.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/devel/api_changes.md b/contributors/devel/api_changes.md
index 0396d6aa..b566e39f 100755
--- a/contributors/devel/api_changes.md
+++ b/contributors/devel/api_changes.md
@@ -215,7 +215,7 @@ runs just prior to conversion. That works fine when the user creates a resource
from a hand-written configuration -- clients can write either field and read
either field, but what about creation or update from the output of GET, or
update via PATCH (see
-[In-place updates](../user-guide/managing-deployments.md#in-place-updates-of-resources))?
+[In-place updates](https://kubernetes.io/docs/user-guide/managing-deployments.md#in-place-updates-of-resources))?
In this case, the two fields will conflict, because only one field would be
updated in the case of an old client that was only aware of the old field (e.g.,
`height`).