fix(v3): Apply suggestions from @sanderson

content/influxdb/cloud-dedicated/admin/databases/_index.md

@@ -17,7 +17,7 @@ related:
 alt_links:
   cloud: /influxdb/cloud/admin/buckets/
   cloud_serverless: /influxdb/cloud-serverless/admin/buckets/
-  clustered: /influxdb/clustered/admin/databases/
+  clustered: /influxdb/cloud-dedicated/admin/databases/
   oss: /influxdb/v2/admin/buckets/
 ---
 
@@ -103,17 +103,18 @@ operating cost of your cluster.
 
 **Default maximum number of columns**: 250
 
+**Configurable maximum number of columns**: 1000
+
 Each row must include a time column, with the remaining columns representing
 tags and fields.
-As a result, a table can have one time column and up to 249 field and tag columns.
+As a result, a table with 250 columns can have one time column and up to
+249 field and tag columns.
 
 If you attempt to write to a table and exceed the column limit, the write
 request fails and InfluxDB returns an error.
 
-When creating or updating a database, you can configure the table column limit to be
-lower than the default or up to 1000, based on your requirements.
-After you update the column limit for a database, the limit applies to newly
-created tables; it doesn't override the column limit for existing tables.
+If you update the column limit for a database, the limit applies to newly
+created tables; doesn't override the column limit for existing tables.
 
 Increasing your column limit affects your {{% product-name omit=" Clustered" %}}
 cluster in the following ways:
@@ -121,6 +122,8 @@ cluster in the following ways:
 {{< expand-wrapper >}}
 {{% expand "May adversely affect system performance" %}}
 
+When creating or updating a database, you can configure the table column limit to be
+lower than the default or up to 1000, based on your requirements.
 InfluxData identified 250 columns as the safe limit for maintaining system
 performance and stability.
 Exceeding this threshold can result in

content/influxdb/cloud-dedicated/admin/databases/update.md

@@ -57,9 +57,11 @@ to update a database in your {{< product-name omit=" Clustered" >}} cluster.
 
     - Database name
     - _Optional_: Database [retention period](/influxdb/cloud-dedicated/admin/databases/#retention-periods).
-    Default is infinite (`0`).
-    - _Optional_: Database table (measurement) limit. Default is `500`.
-    - _Optional_: Database column limit. Default is `250`.
+      Default is infinite (`0`).
+    - _Optional_: Database [table (measurement) limit](/influxdb/cloud-dedicated/admin/databases/#table-limit).
+      Default is `500`.
+    - _Optional_: Database [column limit](/influxdb/cloud-dedicated/admin/databases/#column-limit).
+      Default is `250`.
 
 {{% code-placeholders "DATABASE_NAME|30d|500|200" %}}
 

content/influxdb/cloud-dedicated/write-data/best-practices/schema-design.md

@@ -134,8 +134,9 @@ As a result, a table can have the following:
 If you attempt to write to a table and exceed the column limit, then the write
 request fails and InfluxDB returns an error.
 
-InfluxData identified the default maximum as the safe limit for maintaining system
-performance and stability.
+InfluxData identified the
+[default maximum](/influxdb/cloud-dedicated/admin/databases/#column-limit)
+as the safe limit for maintaining system performance and stability.
 Exceeding this threshold can result in
 [wide schemas](#avoid-wide-schemas), which can negatively impact performance
 and resource use, [depending on your queries](#avoid-non-specific-queries),

content/influxdb/clustered/admin/databases/_index.md

@@ -103,17 +103,18 @@ operating cost of your cluster.
 
 **Default maximum number of columns**: 250
 
+**Configurable maximum number of columns**: 1000
+
 Each row must include a time column, with the remaining columns representing
 tags and fields.
-As a result, a table can have one time column and up to 249 field and tag columns.
+As a result, a table with 250 columns can have one time column and up to
+249 field and tag columns.
 
 If you attempt to write to a table and exceed the column limit, the write
 request fails and InfluxDB returns an error.
 
-When creating or updating a database, you can configure the table column limit to be
-lower than the default or up to 1000, based on your requirements.
-After you update the column limit for a database, the limit applies to newly
-created tables; it doesn't override the column limit for existing tables.
+If you update the column limit for a database, the limit applies to newly
+created tables; doesn't override the column limit for existing tables.
 
 Increasing your column limit affects your {{% product-name omit=" Clustered" %}}
 cluster in the following ways:
@@ -121,6 +122,8 @@ cluster in the following ways:
 {{< expand-wrapper >}}
 {{% expand "May adversely affect system performance" %}}
 
+When creating or updating a database, you can configure the table column limit to be
+lower than the default or up to 1000, based on your requirements.
 InfluxData identified 250 columns as the safe limit for maintaining system
 performance and stability.
 Exceeding this threshold can result in

content/influxdb/clustered/admin/databases/update.md

@@ -26,10 +26,12 @@ to update a database in your {{< product-name omit=" Clustered" >}} cluster.
 2.  Run the `influxctl database update` command and provide the following:
 
     - Database name
-    - _Optional_: Database [retention period](/influxdb/cloud-dedicated/admin/databases/#retention-periods).
-    Default is infinite (`0`).
-    - _Optional_: Database table (measurement) limit. Default is `500`.
-    - _Optional_: Database column limit. Default is `250`.
+    - _Optional_: Database [retention period](/influxdb/clustered/admin/databases/#retention-periods).
+      Default is infinite (`0`).
+    - _Optional_: Database [table (measurement) limit](/influxdb/clustered/admin/databases/#table-limit).
+      Default is `500`.
+    - _Optional_: Database [column limit](/influxdb/clustered/admin/databases/#column-limit).
+      Default is `250`.
 
 {{% code-placeholders "DATABASE_NAME|30d|500|200" %}}
 

content/influxdb/clustered/write-data/best-practices/schema-design.md

@@ -134,8 +134,9 @@ As a result, a table can have the following:
 If you attempt to write to a table and exceed the column limit, then the write
 request fails and InfluxDB returns an error.
 
-InfluxData identified the default maximum as the safe limit for maintaining system
-performance and stability.
+InfluxData identified the
+[default maximum](/influxdb/clustered/admin/databases/#column-limit)
+as the safe limit for maintaining system performance and stability.
 Exceeding this threshold can result in
 [wide schemas](#avoid-wide-schemas), which can negatively impact performance
 and resource use, [depending on your queries](#avoid-non-specific-queries),