diff --git a/docs/content/en/reference/crd/cass-operator-crds-latest/_index.md b/docs/content/en/reference/crd/cass-operator-crds-latest/_index.md
index 154bc7dfb..3a0d04116 100644
--- a/docs/content/en/reference/crd/cass-operator-crds-latest/_index.md
+++ b/docs/content/en/reference/crd/cass-operator-crds-latest/_index.md
@@ -248,8 +248,7 @@ that an update to the secret will trigger an update of the StatefulSets.<br/>
         <td><b>datacenterName</b></td>
         <td>string</td>
         <td>
-          DatacenterName allows to override the name of the Cassandra datacenter. Kubernetes objects will be named after a sanitized version of it if set, and if not metadata.name. In Cassandra the DC name will be overridden by this value.
-It may generate some confusion as objects created for the DC will have a different name than the CasandraDatacenter object itself.
+          DatacenterName allows to override the name of the Cassandra datacenter. In Cassandra the DC name will be overridden by this value.
 This setting can create conflicts if multiple DCs coexist in the same namespace if metadata.name for a DC with no override is set to the same value as the override name of another DC.
 Use cautiously.<br/>
         </td>
@@ -22687,6 +22686,15 @@ with the management API<br/>
             <i>Format</i>: date-time<br/>
         </td>
         <td>false</td>
+      </tr><tr>
+        <td><b>metadataVersion</b></td>
+        <td>integer</td>
+        <td>
+          <br/>
+          <br/>
+            <i>Format</i>: int64<br/>
+        </td>
+        <td>false</td>
       </tr><tr>
         <td><b>nodeReplacements</b></td>
         <td>[]string</td>
diff --git a/docs/content/en/reference/crd/k8ssandra-operator-crds-latest/_index.md b/docs/content/en/reference/crd/k8ssandra-operator-crds-latest/_index.md
index c20926557..55e75c63c 100644
--- a/docs/content/en/reference/crd/k8ssandra-operator-crds-latest/_index.md
+++ b/docs/content/en/reference/crd/k8ssandra-operator-crds-latest/_index.md
@@ -54855,6 +54855,18 @@ the secrets into the necessary resources<br/>
           SecurityContext applied to the Reaper main container.<br/>
         </td>
         <td>false</td>
+      </tr><tr>
+        <td><b>skipSchemaMigration</b></td>
+        <td>boolean</td>
+        <td>
+          Whether to skip schema migration. Schema migration is done in an init container on every Reaper deployment and
+can slow down Reaper's startup time. Besides, schema migration requires reading data at QUORUM. It can be skipped
+if you know that the schema is already up-to-date, or if you know upfront that QUORUM cannot be achieved (for
+example, because a DC is down).<br/>
+          <br/>
+            <i>Default</i>: false<br/>
+        </td>
+        <td>false</td>
       </tr><tr>
         <td><b><a href="#k8ssandraclusterspecreaperstorageconfig">storageConfig</a></b></td>
         <td>object</td>