Skip to content

Commit ec671a5

Browse files
authored
Clarifying a sentence re: backwards compatability
I'm pretty sure this is supposed to say `v1` instead of `v2`.
1 parent bf3667c commit ec671a5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/book/src/multiversion-tutorial/api-changes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ In Kubernetes, **all versions must be safely round-tripable through each
1919
other**. This means that if we convert from version 1 to version 2, and
2020
then back to version 1, we must not lose information. Thus, any change we
2121
make to our API must be compatible with whatever we supported in v1, and
22-
also need to make sure anything we add in v2 is supported in v2. In some
22+
also need to make sure anything we add in v2 is supported in v1. In some
2323
cases, this means we need to add new fields to v1, but in our case, we
2424
won't have to, since we're not adding new functionality.
2525

0 commit comments

Comments
 (0)