Rpk cluster config edits (#1143)

Co-authored-by: Michele Cyran <michele@redpanda.com>

Author: kbatuigas

modules/reference/pages/rpk/rpk-cluster/rpk-cluster-config-edit.adoc

@@ -4,16 +4,15 @@ Edit cluster-wide configuration properties.
 
 This command opens a text editor to modify the cluster's configuration.
 
-Cluster properties are redpanda settings which apply to all nodes in
-the cluster. These are separate to node properties, which are set with
-`rpk redpanda config`.
+Cluster properties are Redpanda settings that apply to all brokers in
+the cluster. These are separate from broker properties, which you can set with `rpk redpanda config`.
 
-Modified values are written back when the file is saved and the editor
-is closed. Properties which are deleted are reset to their default
-values.
+Modified values are saved after the file is saved and the editor
+is closed. If you delete a property, Redpanda resets it to its default
+value.
 
-By default, low level tunables are excluded: use the `--all` flag
-to edit all properties including these tunables.
+By default, low-level tunables are excluded. Use the `--all` flag
+to edit all properties including tunables.
 
 == Usage
 

modules/reference/pages/rpk/rpk-cluster/rpk-cluster-config-export.adoc

@@ -6,8 +6,8 @@ Writes out a YAML representation of the cluster configuration to a file,
 suitable for editing and later applying with the corresponding `import`
 command.
 
-By default, low level tunables are excluded: use the `--all` flag
-to include all properties including these low level tunables.
+By default, low-level tunables are excluded. Use the `--all` flag
+to edit all properties, including these tunables.
 
 == Usage
 
@@ -22,7 +22,7 @@ rpk cluster config export [flags]
 |===
 |*Value* |*Type* |*Description*
 
-|-f, --filename |string |path to file to export to, e.g. './config.yml'.
+|-f, --filename |string |Path to file to export to; for example, `./config.yml`.
 
 |-h, --help |- |Help for export.
 

modules/reference/pages/rpk/rpk-cluster/rpk-cluster-config-force-reset.adoc

@@ -1,17 +1,15 @@
 = rpk cluster config force-reset
 
-Forcibly clear a cluster configuration property on this node.
+Forcibly clear a cluster configuration property on a broker.
 
-This command is not for general changes to cluster configuration: use this only
-when redpanda will not start due to a configuration issue.
+Do not use this command for general changes to cluster configuration. Use `force-reset` only when Redpanda does not start due to a configuration issue; for example, when a property is set to an invalid value or when a property is missing that Redpanda requires to start.
 
-If your cluster is working properly and you would like to reset a property
-to its default, you may use the `set` command with an empty string, or
-use the `edit` command and delete the property`s line.
+This command erases the named property from an internal cache of the cluster configuration on the local broker, so that on next startup Redpanda treats
+the property as if it was set to the default.
 
-This command erases a named property from an internal cache of the cluster
-configuration on the local node, so that on next startup redpanda will treat
-the setting as if it was set to the default.
+If your cluster is working properly and you want to reset a property
+to its default value, either use the `set` command with an empty string, or
+use the `edit` command and delete the line containing the property.
 
 WARNING: Use this command only when Redpanda isn't running.
 
@@ -28,8 +26,8 @@ rpk cluster config force-reset [PROPERTY...] [flags]
 |===
 |*Value* |*Type* |*Description*
 
-|--cache-file |string |location of configuration cache file (defaults to
-redpanda data directory).
+|--cache-file |string |Location of configuration cache file (defaults to
+Redpanda `data` directory).
 
 |-h, --help |- |Help for force-reset.
 

modules/reference/pages/rpk/rpk-cluster/rpk-cluster-config-get.adoc

@@ -2,8 +2,10 @@
 
 Get a cluster configuration property.
 
+ifndef::env-cloud[]
 This command is provided for use in scripts. For interactive editing, or bulk
 output, use the `edit` and `export` commands respectively.
+endif::[]
 
 == Usage
 

modules/reference/pages/rpk/rpk-cluster/rpk-cluster-config-import.adoc

@@ -4,11 +4,7 @@ CAUTION: Redpanda does not support importing cluster-specific identification (su
 
 Import cluster configuration from a file.
 
-Import configuration from a YAML file, usually generated with
-corresponding `export` command. This downloads the current cluster
-configuration, calculates the difference with the YAML file, and
-updates any properties that were changed. If a property is removed
-from the YAML file, it is reset to its default value.
+This command imports a cluster configuration from a YAML file, typically generated with the `export` command. The command first retrieves the current cluster configuration, compares it with the specified YAML file, and then updates any properties that were changed. If a property exists in the current configuration but is absent from the YAML file, that property is reset to its default value.
 
 == Usage
 
@@ -23,8 +19,8 @@ rpk cluster config import [flags]
 |===
 |*Value* |*Type* |*Description*
 
-|-f, --filename |string |full path to file to import, e.g.
-'/tmp/config.yml'.
+|-f, --filename |string |Full path to file to import; for example,
+`/tmp/config.yml`.
 
 |-h, --help |- |Help for import.
 

modules/reference/pages/rpk/rpk-cluster/rpk-cluster-config-lint.adoc

@@ -2,8 +2,8 @@
 
 Remove any deprecated content from `redpanda.yaml`.
 
-Deprecated content includes properties which were set via `redpanda.yaml`
-in earlier versions but are now managed via Redpanda`s central configuration store (and via `rpk cluster config edit`).
+Deprecated content includes properties that were set in the `redpanda.yaml` file 
+in earlier versions but are now managed through Redpanda's central configuration store and through `rpk cluster config edit`.
 
 == Usage