Review suggestion - doc

Signed-off-by: Florent Poinsard <[email protected]>
planetscale · Oct 11, 2024 · 91eb524 · 91eb524
1 parent 2f9c6fb
commit 91eb524
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 8 deletions.
diff --git a/docs/api/index.html b/docs/api/index.html
@@ -6553,10 +6553,10 @@ <h3 id="planetscale.com/v2.VitessKeyspaceTemplateImages">VitessKeyspaceTemplateI
 <p>VitessKeyspaceTemplateImages specifies user-definable container images to
 use for this keyspace. The images defined here by the user will override
 those defined at the top-level in VitessCluster.spec.images.</p>
-<p>While this field allows you to set a different set of Vitess version for
-some components of Vitess than the version defined at the top level, it
-is important to note that Vitess only ensure compatibility between one
-version and the next and previous one. For instance: N is only compatible
+<p>While this field allows you to set a different Vitess version for some
+components than the version defined at the top level, it is important to
+note that Vitess only ensures compatibility between one version and the
+next and previous one. For instance: N is only guaranteed  to be compatible
 with N+1 and N-1. Do be careful when specifying multiple versions across
 your cluster so that they respect this compatibility rule.</p>
 <p>Note: this structure is a copy of VitessKeyspaceImages, once we have gotten

diff --git a/pkg/apis/planetscale/v2/vitesskeyspace_types.go b/pkg/apis/planetscale/v2/vitesskeyspace_types.go
@@ -191,10 +191,10 @@ type VitessKeyspaceTemplate struct {
 // use for this keyspace. The images defined here by the user will override
 // those defined at the top-level in VitessCluster.spec.images.
 //
-// While this field allows you to set a different set of Vitess version for
-// some components of Vitess than the version defined at the top level, it
-// is important to note that Vitess only ensure compatibility between one
-// version and the next and previous one. For instance: N is only compatible
+// While this field allows you to set a different Vitess version for some
+// components than the version defined at the top level, it is important to
+// note that Vitess only ensures compatibility between one version and the
+// next and previous one. For instance: N is only guaranteed  to be compatible
 // with N+1 and N-1. Do be careful when specifying multiple versions across
 // your cluster so that they respect this compatibility rule.
 //