Configuring Console when deployed using operator chart

There are some contradictions related to the Console configuration.

1. This page says:

When you deploy a Redpanda cluster using the [Redpanda Operator or Redpanda Helm chart](https://docs.redpanda.com/current/deploy/redpanda/kubernetes/k-production-deployment/), 
Redpanda Console is automatically deployed alongside your cluster. 

I can confirm, indeed, when I deployed the operator, the Console CR was created and console was successfully deployed along with the rest of the components. All the values like brokers etc are nicely pre-populated and console works right out of the box.

2. This page, for the operator says:

Configure Redpanda Console in the console section of your Redpanda custom resource:

And right below that statement there is a code snippet for the Console CR, not the Redpanda one.

3. The API doc for the RedpandaClusterSpec says that console is Deprecated: Use the dedicated Console CRD.

The question is - how do we configure the console if the Console CR is automatically created by the operator? I need to make just small adjustments, while I don't want to loose any pre-populated parameters.

Start with the linked Console deployment, Console configuration, and RedpandaClusterSpec API documentation pages, comparing their descriptions of operator-managed configuration. Clarify the supported configuration path and how existing pre-populated values are retained; done when the three pages consistently explain how to make small Console adjustments.