diff options
| author | Jimmy Cuadra <jimmy@jimmycuadra.com> | 2016-10-27 23:16:31 -1000 |
|---|---|---|
| committer | Jimmy Cuadra <jimmy@jimmycuadra.com> | 2016-11-05 00:17:28 -0700 |
| commit | 76480357f53da80b60595ea3365c692e90953e0e (patch) | |
| tree | 14d4f73bd0a81ef94ad39224f0d5a03d3bc5e010 | |
| parent | a12debe4659f3e426193aaea6291590b6df2c01d (diff) | |
Rename PetSet to StatefulSet in docs and examples.
| -rw-r--r-- | updating-docs-for-feature-changes.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/updating-docs-for-feature-changes.md b/updating-docs-for-feature-changes.md index 6e85c48d..309b809d 100644 --- a/updating-docs-for-feature-changes.md +++ b/updating-docs-for-feature-changes.md @@ -11,7 +11,7 @@ Anyone making user facing changes to kubernetes. This is especially important f ### When making Api changes *e.g. adding Deployments* -* Always make sure docs for downstream effects are updated *(PetSet -> PVC, Deployment -> ReplicationController)* +* Always make sure docs for downstream effects are updated *(StatefulSet -> PVC, Deployment -> ReplicationController)* * Add or update the corresponding *[Glossary](http://kubernetes.io/docs/reference/)* item * Verify the guides / walkthroughs do not require any changes: * **If your change will be recommended over the approaches shown in these guides, then they must be updated to reflect your change** |