fix links and redirects

blueprints/autostart-internal-apps.html.md

@@ -10,7 +10,7 @@ To use the Fly Proxy autostart and autostop feature you need to configure servic
 
 This blueprint focuses on using autostart and autostop to control Machines based on incoming requests. But when you use Flycast for private apps you also get other Fly Proxy features like geographically aware load balancing.
 
-Learn more about [Flycast](/docs/networking/private-networking/#flycast-private-fly-proxy-services).
+Learn more about [Flycast](/docs/networking/flycast/).
 
 ## Create a new private app with a Flycast address
 

blueprints/connect-private-network-wireguard/index.html.md

@@ -11,7 +11,7 @@ date: 2024-06-14
 
 <center><iframe width="600" height="315" src="https://www.youtube-nocookie.com/embed/4NcvlIlIlso?si=DPbDPwzlRTQFx0hB" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></center><br />
 
-Every [Fly.io](http://Fly.io) organization comes with a [private network](https://fly.io/docs/networking/private-networking/) that lets all your apps connect to each other. This is super convenient when you need to have microservices call each other’s endpoints or use [Flycast](https://fly.io/docs/networking/private-networking/#flycast-private-fly-proxy-services) to let your private apps turn off when you’re not using them. However, this isn’t just limited to your apps. You can jack into this network with WireGuard.
+Every [Fly.io](http://Fly.io) organization comes with a [private network](https://fly.io/docs/networking/private-networking/) that lets all your apps connect to each other. This is super convenient when you need to have microservices call each other’s endpoints or use [Flycast](/docs/networking/flycast/) to let your private apps turn off when you’re not using them. However, this isn’t just limited to your apps. You can jack into this network with WireGuard.
 
 This blueprint shows you how to create a WireGuard peer to your private network and connect to it so that you can access it from anywhere.
 

networking/flycast.html.markerb

@@ -2,9 +2,7 @@
 title: "Flycast - Private Fly Proxy services"
 layout: docs
 nav: firecracker
-redirect_from:
-  - /docs/reference/privatenetwork/
-  - /docs/reference/private-networking/
+redirect_from: /docs/networking/private-networking/#flycast-private-fly-proxy-services
 ---
 
 Flycast is the Fly.io version of Anycast, but for private apps on private networks. With Flycast, requests to your private apps get routed through the Fly Proxy, rather than Machine-to-Machine using `.internal` addresses (the [private networking](/docs/networking/private-networking/) available by default on every app). Unlike `.internal` addresses, with a Flycast address, you don't need to keep Machines running for the app to be reachable.

reference/fly-proxy.html.markerb

@@ -27,7 +27,7 @@ Fly Proxy gets all its information about apps and Machines and services from cor
 
 ## How Fly Proxy routes requests over your private network (6PN)
 
-Apps can communicate with each other by default on your [private network](/docs/networking/private-networking/) without Fly Proxy's help, but if you want to use Fly Proxy features, then you can do that with [Flycast](/docs/networking/private-networking/#flycast-private-fly-proxy-services).
+Apps can communicate with each other by default on your [private network](/docs/networking/private-networking/) without Fly Proxy's help, but if you want to use Fly Proxy features, then you can do that with [Flycast](/docs/networking/flycast/).
 
 When you assign a Flycast address to your app, the traffic gets routed through Fly Proxy while remaining entirely in your private network. When App 1 makes a request to App 2 in the same private network, Fly Proxy on the worker hosting App 1's Machines checks out the details of the request, adds the appropriate headers, and routes the request through the same WireGuard tunnel backhaul to the nearest healthy worker that hosts Machines for App 2. Fly Proxy on that server sends the request to a Machine running App 2.