add peer discovery guide

docs/overview/concepts/peer-discovery.md

@@ -12,7 +12,7 @@ Once a connection is established, the node must actively seek out additional pee
 
 Waku supports multiple peer discovery mechanisms, such as:
 
-- [Configuring Predefined Nodes](/overview/concepts/predefined-nodes)
+- [Configuring Static Peers](/overview/concepts/static-peers)
 - [Peer Discovery via DNS](/overview/concepts/dns-discovery)
 - [Discv5 Ambient Peer Discovery](/overview/concepts/discv5)
 - [Peer Exchange](/overview/concepts/peer-exchange)

docs/overview/concepts/static-peers.md

@@ -1,8 +1,8 @@
 ---
-title: Predefined Nodes
+title: Static Peer
 ---
 
-Waku applications have the flexibility to embed bootstrap node addresses directly into their codebase. Developers can use either the [predefined nodes by Status](https://github.com/waku-org/js-waku/blob/master/packages/core/src/lib/predefined_bootstrap_nodes.ts#L45) or [run a node](/guides/nodes-and-sdks#run-a-waku-node) per their preference.
+Waku applications have the flexibility to embed bootstrap node addresses directly into their codebase. Developers can either use [static peers by Status](https://github.com/waku-org/js-waku/blob/master/packages/core/src/lib/predefined_bootstrap_nodes.ts#L45) or [run a node](/guides/nodes-and-sdks#run-a-waku-node) per their preference.
 
 #### Pros
 
@@ -18,7 +18,7 @@ Waku applications have the flexibility to embed bootstrap node addresses directl
 ## Overview
 
 ```mdx-code-block
-import PredefinedNodes from "@site/diagrams/_predefined-nodes.md";
+import StaticPeers from "@site/diagrams/_static-peers.md";
 
-<PredefinedNodes />
+<StaticPeers />
 ```