In MySQL 8.0.22 and later, the SHOW SLAVE STATUS command and the Master_Host column are deprecated in favor of SHOW REPLICA STATUS and Source_Host. Since the examples in this documentation use MySQL 8.4.8 (LTS), it is recommended to use the modern syntax for better alignment with current best practices.

The term 'Master-slave' is deprecated in official MySQL documentation in favor of 'Source-Replica'. While the CLI flag --topology=master-slave remains for technical compatibility, updating the label in the documentation table improves clarity and adheres to modern terminology standards.

The tables in this page use || at the start of header/separator rows (e.g., || Flavor | ...). Standard Markdown tables use single | delimiters; the doubled pipes can break rendering in Astro/Markdown processors. Update these rows to the standard | col | col | format so the tables render consistently with the rest of the docs site.

Same as above: this versions/status table uses || prefixes. Please convert it to a standard Markdown table (single | delimiters) to ensure it renders correctly.

The minimum version for InnoDB Cluster is documented as 8.0, but the implementation enforces 8.0.11+ (it errors with “InnoDB Cluster requires MySQL 8.0.11 or later”). Please update the min-version column to 8.0.11 to match actual behavior.

This page says dbdeployer versions will show cluster_8.4.8 after unpacking, but dbdeployer versions lists the binary directory names (and unpack names the directory as --prefix + version). Unless the user supplies --prefix, unpacking mysql-cluster-8.4.8... results in a directory like 8.4.8, not cluster_8.4.8. Please adjust the example/output (and, if you want a visible prefix like ndb8.4.8, show using dbdeployer unpack --prefix=ndb ...).

The deploy example uses dbdeployer deploy replication 8.4.8 --topology=ndb, but earlier the page implies a prefixed version label. To avoid confusion, make the version argument consistent with whatever directory name you tell users to create (e.g., 8.4.8 if no prefix, or ndb8.4.8 if using --prefix=ndb).

The sample check_cluster output shows node ports 3310/3320/3330, but InnoDB Cluster port allocation is based on the InnoDB Cluster base port range (defaults to 21000 + offsets) rather than the classic 3310/3320/3330 pattern. Consider updating the example output to reflect the actual ports users will see (or omit specific port numbers to keep it accurate across configurations).

This wsrep example refers to node1/ node2/ node3/ in the layout, but the command examples use n1/n2/n3 helper scripts. If the intent is to show the helper scripts, consider updating the directory tree comments to mention that n1, n2, n3 scripts are generated alongside node1/.. to avoid confusion for first-time users.

The check_nodes script for Group Replication runs select * from performance_schema.replication_group_members on each node (raw output), but this page describes it as a summarized status report and shows example lines like # node 1 - ONLINE (PRIMARY). Please update the description/example output to match what the script actually prints.

The PXC check_nodes script prints a header per node and then the raw SHOW GLOBAL STATUS ... wsrep_* result set, but the example output here is a single-line summary per node. Please adjust the example to match the real script output (or describe it generically without hardcoding an output format).

~/sandboxes/.../check_nodes in NDB deployments is generated from the ndb_mgm template (it launches the NDB management client). It won’t print status by itself unless arguments are provided. The example here implies check_nodes outputs status directly; consider changing it to something like check_nodes -e show / check_nodes -e "ALL STATUS", or document that check_nodes opens ndb_mgm and users should pass -e commands.