fix: update incorrect filenames

Author: gyan-sharma

content/docs/platform-components/blockchain-infrastructure/blockchain-nodes.mdx

@@ -276,8 +276,7 @@ and the process is repeated. IBFT 2.0 has immediate finality. There are no forks
 and all valid blocks are included in the main chain.
 
 When you deploy a Hyperledger Besu blockchain network on SettleMint, it should
-be Byzantine fault tolerance.
-[More about the number of nodes you need](node-types)
+be Byzantine fault tolerant.
 
 More information on Hyperledger Besu can be found in the official
 [Hyperledger Besu documentation](https://besu.hyperledger.org/en/stable/).

…rmissioned-networks/Hyperledger-Besu.mdx …rmissioned-networks/hyperledger-besu.mdxcontent/docs/supported-blockchains/permissioned-networks/Hyperledger-Besu.mdx renamed to content/docs/supported-blockchains/permissioned-networks/hyperledger-besu.mdx content/docs/supported-blockchains/permissioned-networks/Hyperledger-Besu.mdx renamed to content/docs/supported-blockchains/permissioned-networks/hyperledger-besu.mdx

@@ -89,8 +89,7 @@ optimizations for large validator sets, making it better suited for
 enterprise-grade and high-throughput networks.
 
 When you deploy a Hyperledger Besu blockchain network on SettleMint, it should
-be Byzantine fault tolerance.
-[More about the number of nodes you need](node-types)
+be Byzantine fault tolerant.
 
 More information on Hyperledger Besu can be found in the official
 [Hyperledger Besu documentation](https://besu.hyperledger.org/en/stable/).