refactor: remove redundant overview article + edit links to comply with OCL's Pattern guide

Author: anegg0

…-docs/run-arbitrum-node/02-node-types.md …docs/run-arbitrum-node/01-node-types.mdxarbitrum-docs/run-arbitrum-node/02-node-types.md renamed to arbitrum-docs/run-arbitrum-node/01-node-types.mdx arbitrum-docs/run-arbitrum-node/02-node-types.md renamed to arbitrum-docs/run-arbitrum-node/01-node-types.mdx

@@ -8,14 +8,13 @@ content_type: overview
 ---
 
 import PublicPreviewBannerPartial from '../partials/_public-preview-banner-partial.mdx';
+import { VanillaAdmonition } from '@site/src/components/VanillaAdmonition/';
 
-<PublicPreviewBannerPartial />
-
-:::info
+<VanillaAdmonition type="note">
 
 There is no protocol level incentive to run an Arbitum full node. If you’re interested in accessing an Arbitrum chain, but you don’t want to set up your own node, see our [RPC endpoints and providers](/build-decentralized-apps/reference/01-node-providers.mdx) to get RPC access to fully-managed nodes hosted by a third party provider.
 
-:::
+</VanillaAdmonition>
 
 :::caution API security disclaimer
 
@@ -39,24 +38,24 @@ When it comes to interacting with the Arbitrum network, users have the option to
 - Reduced trust requirements: By running a full node, users can interact with the Arbitrum network without relying on third-party services or infrastructure. This reduces the need to trust external entities and mitigates the risk of potential centralized failures or vulnerabilities.
 - Lower resource requirements: Compared to archive nodes, full nodes generally require fewer resources such as storage and computational power. This makes them more accessible to users with limited hardware capabilities or those operating on resource-constrained environments.
 
-For detailed instructions on how to run an Arbitrum full node, see [here](/run-arbitrum-node/03-run-full-node.mdx).
+For detailed instructions, read [how to run an Arbitrum full node](/run-arbitrum-node/03-run-full-node.mdx).
 
 ### Considerations for running an Arbitrum archive node
 
 While full nodes offer numerous advantages, there are situations where running an archive node may be more appropriate. Archive nodes store the complete history of the Arbitrum network, making them suitable for users who require extensive historical data access or advanced analytical purposes. However, it's important to note that archive nodes are more resource-intensive, requiring significant storage capacity and computational power.
 
-For detailed instructions on how to run an Arbitrum archive node, see [here](/run-arbitrum-node/more-types/01-run-archive-node.mdx).
+For detailed instructions, read [how to run an Arbitrum archive node](/run-arbitrum-node/more-types/01-run-archive-node.mdx).
 
 ### Considerations for running an Arbitrum classic node
 
-The significance of running an Arbitrum classic node is mainly applicable to individuals with specific needs for an archive node and access to classic-related commands. More details can be found [here](/run-arbitrum-node/more-types/01-run-archive-node.mdx).
+The significance of running an Arbitrum classic node is mainly applicable to individuals with specific needs for an archive node and access to classic-related commands. More details can be found [here]().
 
-For detailed instructions on how to run an Arbitrum classic node, see [here](/run-arbitrum-node/more-types/03-run-classic-node.mdx).
+For detailed instructions, read [how to run an Arbitrum classic node](/run-arbitrum-node/more-types/03-run-classic-node.mdx).
 
 ### Considerations for running a feed relay
 
 If you are running a single node, there is no requirement to set up a feed relay. However, if you have multiple nodes, it is highly recommended to have a single feed relay per datacenter. This setup offers several advantages such as reducing ingress fees and enhancing stability within the network.
 
 In the near future, feed endpoints will mandate compression using a custom dictionary. Therefore, if you plan to connect to a feed using anything other than a standard node, it is strongly advised to run a local feed relay. This will ensure that you have access to an uncompressed feed by default, maintaining optimal performance and compatibility.
 
-For detailed instructions on how to run a feed relay, see [here](/run-arbitrum-node/sequencer/01-run-feed-relay.mdx).
+For detailed instructions, read [how to run an Arbitrum feed relay](/run-arbitrum-node/sequencer/01-run-feed-relay.mdx).