Merge pull request #11236 from tsuzu/fix-typo

k8s-ci-robot · web-flow · commit 65fbabe1cf55 · 2024-09-30T07:20:02.000+01:00
📖 Fix typos
diff --git a/config/metrics/templates/README.md b/config/metrics/templates/README.md
@@ -1,6 +1,6 @@
 # Metrics
 
-**Disclamer**: This is a temporary workaround. The long-term goal is to generate metric configuration from API type markers.
+**Disclaimer**: This is a temporary workaround. The long-term goal is to generate metric configuration from API type markers.
 
 The make target `generate-metrics-config` is used to generate a single file which contains the Cluster API specific custom resource configuration for kube-state-metrics.
 
diff --git a/docs/book/src/developer/providers/migrations/v1.8-to-v1.9.md b/docs/book/src/developer/providers/migrations/v1.8-to-v1.9.md
@@ -28,4 +28,4 @@ maintainers of providers and consumers of our Go API.
 
 ### Suggested changes for providers
 
-- The Errors package was created when capi provider implementation was running as machineActuators that needed to vendor core capi to function. There is no usage recommendations today and its value is questionable since we moved to CRDs that inter-operate mostly via conditions. Instead we plan to drop the dedicated semantic for terminal failure and keep improving Machine lifecycle signal through conditions. Therefore the Errors package [has been deprecated in v1.8](https://github.com/kubernetes-sigs/cluster-api/issues/10784). It's recommented to remove any usage of the currently exported variables.
+- The Errors package was created when capi provider implementation was running as machineActuators that needed to vendor core capi to function. There is no usage recommendations today and its value is questionable since we moved to CRDs that inter-operate mostly via conditions. Instead we plan to drop the dedicated semantic for terminal failure and keep improving Machine lifecycle signal through conditions. Therefore the Errors package [has been deprecated in v1.8](https://github.com/kubernetes-sigs/cluster-api/issues/10784). It's recommended to remove any usage of the currently exported variables.
diff --git a/docs/book/src/reference/api/metadata-propagation.md b/docs/book/src/reference/api/metadata-propagation.md
@@ -63,7 +63,7 @@ Top-level labels that meet a specific cretria are propagated to the Node labels
 - `.labels.[label-meets-criteria]` => `Node.labels`
 - `.annotations` => Not propagated.
 
-Label should meet one of the following criterias to propagate to Node: 
+Label should meet one of the following criteria to propagate to Node: 
 - Has `node-role.kubernetes.io` as prefix.
 - Belongs to `node-restriction.kubernetes.io` domain.
 - Belongs to `node.cluster.x-k8s.io` domain.  

Original file line number	Diff line number	Diff line change
`@@ -28,4 +28,4 @@ maintainers of providers and consumers of our Go API.`
`28`	`28`
`29`	`29`	`### Suggested changes for providers`
`30`	`30`
`31`		-- The Errors package was created when capi provider implementation was running as machineActuators that needed to vendor core capi to function. There is no usage recommendations today and its value is questionable since we moved to CRDs that inter-operate mostly via conditions. Instead we plan to drop the dedicated semantic for terminal failure and keep improving Machine lifecycle signal through conditions. Therefore the Errors package [has been deprecated in v1.8](https://github.com/kubernetes-sigs/cluster-api/issues/10784). It's recommented to remove any usage of the currently exported variables.
	`31`	+- The Errors package was created when capi provider implementation was running as machineActuators that needed to vendor core capi to function. There is no usage recommendations today and its value is questionable since we moved to CRDs that inter-operate mostly via conditions. Instead we plan to drop the dedicated semantic for terminal failure and keep improving Machine lifecycle signal through conditions. Therefore the Errors package [has been deprecated in v1.8](https://github.com/kubernetes-sigs/cluster-api/issues/10784). It's recommended to remove any usage of the currently exported variables.