> I would prefer you don't use the same name for profile and device, e.g. in step 1 where you use 'bridge0' as both profilename and device name.

You can set the profile name to a value other than the interface name, but it's also common practice to name the profile the same as the interface name - especially if there's just one connection profile for an interface.
In our docs it's intentional that we use the interface name also as the profile name. Especially in procedures that involve different interfaces/connections this way it's easier to see which interface is used in which profile.



> In step 3, please use the same device in the examples for adding a new and an existing device.

It's also intentional that we use different devices for new and existing devices in this procedure.
The reason why we use both Ethernet devices and bonds is to show the different commands
based on whether a profile already exists (in the example, the bonds) or not (Ethernet).

Step 2 lists two Ethernet devices (not used in any profile yet) and two bonds (for which profiles exists).
The procedure would not work if step 3 would modify (non-existent) profiles for enp7s0 and enp8s0.



> In step 7, this formulation  is difficult to understand, please consider reformulate:
> "Red Hat Enterprise Linux activates controller and ports when the system boots. By activating any port connection,
> the controller is also activated. However, in this case, only one port connection is activated. By default,
> activating the controller does not automatically activate the ports. However, you can enable this behavior by setting:"

First I thought it's clear, but after reading the paragraph ten times, I also got doubts what happens. :-) I rephrase the paragraph:
"When you activate any port of the connection, NetworkManager also activates the bridge, but not the other ports of it. You can configure that Red Hat Enterprise Linux enables all ports automatically when when the bridge is enabled: ..."

The updated paragraph in step 7 is now available on the Customer Portal:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9-beta/html/configuring_and_managing_networking/configuring-a-network-bridge_configuring-and-managing-networking#configuring-a-network-bridge-using-nmcli-commands_configuring-a-network-bridge