Update versioned_docs/version-23.10.3/private-networks/how-to/configu…

…re/bootnodes.md

Co-authored-by: Sally MacFarlane <macfarla.github@gmail.com>
Signed-off-by: Gabriel-Trintinalia <gabriel.trintinalia@consensys.net>

versioned_docs/version-23.10.3/private-networks/how-to/configure/bootnodes.md

@@ -42,7 +42,7 @@ By default, peer discovery listens on all available network interfaces. If the d
 
 ## Configure bootnodes in a production network
 
-A network must have at least one operating bootnode. To allow for continuity in the event of failure, configure two or more bootnodes in a production network. In case of no bootnodes, Mainnet default bootnodes will be used.
+A network must have at least one operating bootnode. To allow for continuity in the event of failure, configure two or more bootnodes in a production network. If you don't configure any bootnodes, Mainnet default bootnodes will be used.
 
 We don't recommend putting bootnodes behind a load balancer because the [enode](../../../public-networks/concepts/node-keys.md#enode-url) relates to the node public key, IP address, and discovery ports. Any changes to a bootnode enode prevents other nodes from being able to establish a connection with the bootnode. This is why we recommend putting more bootnodes on the network itself.