fix(vpc): added to menu

Author: RoRoJ

menu/navigation.json

@@ -3211,6 +3211,10 @@
                   {
                     "label": "I can't delete my VPC or Private Network",
                     "slug": "cant-delete-vpc-pn"
+                  },
+                  {
+                    "label": "I'm experiencing connectivity or routing issues",
+                    "slug": "vpc-pn-routing-connectivity-issues"
                   }
                 ],
                 "label": "Troubleshooting",

pages/ipam/reference-content/public-connectivity-best-practices.mdx

@@ -49,7 +49,7 @@ In the future, look out for even more improvements to our flexible IP offering,
 We strongly recommend that you disable public connectivity on all of your Scaleway resources, unless it is absolutely required. Attaching resources to Private Networks, and limiting their communication to these networks brings the following advantages:
 
 - **Minimized attack surface**: Without a public IP address, the resource is not exposed directly to the internet, decreasing the risk of DDoS or brute force attacks, or unauthorized access.
-- **Reduced cost**: Public (flexible) IP addresses are [billed](https://www.scaleway.com/en/pricing/), whereas Private Networks and the private IP addresses that attach resources to Private Networks are free of charge (except for Elastic Metal servers). 
+- **Reduced cost**: Public (flexible) IP addresses are [billed](https://www.scaleway.com/en/pricing/), whereas Private Networks and the private IP addresses that attach resources to Private Networks are free of charge (except for Elastic Metal servers and Apple silicon). 
 - **Improved latency**: Communication between resources over a Private Network is generally faster, as it does not need to be routed through the public internet.
 
 Depending on the resource type, public connectivity can be disabled by: