run make generate

docs/documents/apis.md

@@ -2607,10 +2607,9 @@ k8s.io/apimachinery/pkg/util/intstr.IntOrString
 Value can be an absolute number (ex: 5) or a percentage of desired machines (ex: 10%).
 Absolute number is calculated from percentage by rounding down.
 This can not be 0 if MaxSurge is 0.
-By default, a fixed value of 1 is used.
-Example: when this is set to 30%, the old MC can be scaled down to 70% of desired machines
-immediately when the rolling update starts. Once new machines are ready, old MC
-can be scaled down further, followed by scaling up the new MC, ensuring
+Example: when this is set to 30%, the old machine set can be scaled down to 70% of desired machines
+immediately when the rolling update starts. Once new machines are ready, old machine set
+can be scaled down further, followed by scaling up the new machine set, ensuring
 that the total number of machines available at all times during the update is at
 least 70% of desired machines.</p>
 </td>
@@ -2633,12 +2632,11 @@ machines.
 Value can be an absolute number (ex: 5) or a percentage of desired machines (ex: 10%).
 This can not be 0 if MaxUnavailable is 0.
 Absolute number is calculated from percentage by rounding up.
-By default, a value of 1 is used.
-Example: when this is set to 30%, the new MC can be scaled up immediately when
-the rolling update starts, such that the total number of old and new machines do not exceed
+Example: when this is set to 30%, the new machine set can be scaled up immediately when
+the rolling update starts, such that the total number of old and new machines does not exceed
 130% of desired machines. Once old machines have been killed,
-new MC can be scaled up further, ensuring that total number of machines running
-at any time during the update is atmost 130% of desired machines.</p>
+new machine set can be scaled up further, ensuring that total number of machines running
+at any time during the update is utmost 130% of desired machines.</p>
 </td>
 </tr>
 </tbody>

kubernetes/crds/machine.sapcloud.io_machinedeployments.yaml

@@ -179,12 +179,11 @@ spec:
                           Value can be an absolute number (ex: 5) or a percentage of desired machines (ex: 10%).
                           This can not be 0 if MaxUnavailable is 0.
                           Absolute number is calculated from percentage by rounding up.
-                          By default, a value of 1 is used.
-                          Example: when this is set to 30%, the new MC can be scaled up immediately when
-                          the rolling update starts, such that the total number of old and new machines do not exceed
+                          Example: when this is set to 30%, the new machine set can be scaled up immediately when
+                          the rolling update starts, such that the total number of old and new machines does not exceed
                           130% of desired machines. Once old machines have been killed,
-                          new MC can be scaled up further, ensuring that total number of machines running
-                          at any time during the update is atmost 130% of desired machines.
+                          new machine set can be scaled up further, ensuring that total number of machines running
+                          at any time during the update is utmost 130% of desired machines.
                         x-kubernetes-int-or-string: true
                       maxUnavailable:
                         anyOf:
@@ -195,10 +194,9 @@ spec:
                           Value can be an absolute number (ex: 5) or a percentage of desired machines (ex: 10%).
                           Absolute number is calculated from percentage by rounding down.
                           This can not be 0 if MaxSurge is 0.
-                          By default, a fixed value of 1 is used.
-                          Example: when this is set to 30%, the old MC can be scaled down to 70% of desired machines
-                          immediately when the rolling update starts. Once new machines are ready, old MC
-                          can be scaled down further, followed by scaling up the new MC, ensuring
+                          Example: when this is set to 30%, the old machine set can be scaled down to 70% of desired machines
+                          immediately when the rolling update starts. Once new machines are ready, old machine set
+                          can be scaled down further, followed by scaling up the new machine set, ensuring
                           that the total number of machines available at all times during the update is at
                           least 70% of desired machines.
                         x-kubernetes-int-or-string: true