From b1fb89cc5cdc5bdfbd13ff205b8ea659e71c7eb7 Mon Sep 17 00:00:00 2001 From: AdamDang Date: Sat, 2 Jun 2018 17:55:50 +0800 Subject: Typo fix: A users-> A user A users-> A user --- contributors/design-proposals/apps/statefulset-update.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contributors/design-proposals/apps/statefulset-update.md b/contributors/design-proposals/apps/statefulset-update.md index 27d3000f..b4089011 100644 --- a/contributors/design-proposals/apps/statefulset-update.md +++ b/contributors/design-proposals/apps/statefulset-update.md @@ -747,7 +747,7 @@ kubectl rollout undo statefulset web ### Rolling Forward Rolling back is usually the safest, and often the fastest, strategy to mitigate deployment failure, but rolling forward is sometimes the only practical solution -for stateful applications (e.g. A users has a minor configuration error but has +for stateful applications (e.g. A user has a minor configuration error but has already modified the storage format for the application). Users can use sequential `kubectl apply`'s to update the StatefulSet's current [target state](#target-state). The StatefulSet's `.Spec.GenerationPartition` -- cgit v1.2.3