Fix API links for v0.5.

contrib/dyn_templates/src/lib.rs

@@ -79,7 +79,7 @@
 //! See the [configuration chapter] of the guide for more information on
 //! configuration.
 //!
-//! [configuration chapter]: https://rocket.rs/master/guide/configuration
+//! [configuration chapter]: https://rocket.rs/v0.5/guide/configuration
 //!
 //! ## Template Naming and Content-Types
 //!

docs/guide/11-deploying.md

@@ -92,10 +92,10 @@ The following section addresses these concerns and more for common deployment
 scenarios.
 
 [DDoS mitigation]: @github/issues/1405
-[graceful shutdown]: @api/master/rocket/shutdown/struct.ShutdownConfig.html
-[`Shutdown`]: @api/master/rocket/struct.Shutdown.html
-[shutdown fairings]: @api/master/rocket/fairing/trait.Fairing.html#shutdown
-[triggers]: @api/master/rocket/shutdown/struct.ShutdownConfig.html#triggers
+[graceful shutdown]: @api/v0.5/rocket/shutdown/struct.ShutdownConfig.html
+[`Shutdown`]: @api/v0.5/rocket/struct.Shutdown.html
+[shutdown fairings]: @api/v0.5/rocket/fairing/trait.Fairing.html#shutdown
+[triggers]: @api/v0.5/rocket/shutdown/struct.ShutdownConfig.html#triggers
 
 ## Common Scenarios
 
@@ -217,8 +217,8 @@ Our recommendation for a direct self-managed deployment is to:
     be explicitly configured via [`proxy_proto_header`] for Rocket to consider.
 
 [`cargo-zigbuild`]: https://github.com/rust-cross/cargo-zigbuild
-[`ip_header`]: @api/master/rocket/config/struct.Config.html#structfield.ip_header
-[`proxy_proto_header`]: @api/master/rocket/config/struct.Config.html#structfield.proxy_proto_header
+[`ip_header`]: @api/v0.5/rocket/config/struct.Config.html#structfield.ip_header
+[`proxy_proto_header`]: @api/v0.5/rocket/config/struct.Config.html#structfield.proxy_proto_header
 
 ### Containerization