doc: remove 3rd shard from 2 shard global cluster example

[BassT]

Description

Please include a summary of the fix/feature/change, including any relevant motivation and context.

Link to any related issue(s):

Type of change:

• Bug fix (non-breaking change which fixes an issue). Please, add the "bug" label to the PR.
• New feature (non-breaking change which adds functionality). Please, add the "enhancement" label to the PR.
• Breaking change (fix or feature that would cause existing functionality to not work as expected). Please, add the "breaking change" label to the PR.
• This change requires a documentation update
• Documentation fix/enhancement

Required Checklist:

• I have signed the MongoDB CLA
• I have read the contribution guidelines
• I have added tests that prove my fix is effective or that my feature works per HashiCorp requirements
• I have added any necessary documentation (if appropriate)
• I have run make fmt and formatted my code

Further comments

[andreaangiolillo]

Hi @BassT,
Thank you for your contribution! Could you kindly provide some additional clarification regarding the changes made in your PR? Specifically, in the example provided, the definition outlines a scenario where there's a global cluster spanning across 2 zones, and within each zone, there are 3 shards.

[BassT]

Hi @andreaangiolillo,

The comment in line 61 suggests that "zone n2" is supposed to be a 2-shard zone but lists 3 shards.

"shard n3" in "zone n2" falls out of line because it's the only shard located in the US while the other two shards of this zone are located in Europe.

For the sake of clarity I suggest removing "shard n3" of "zone n2". Alternatively, the comment on "zone n2" could be changed to "3-shard Multi-Cloud Cluster" and the region of "shard n3" to one in Europe.

[andreaangiolillo]

I see, thanks for the clarification!

[andreaangiolillo]

LGTM