Fix broken url_for targets.

These were not detected before due to a linkchecker vs. subdomain gotcha
(GH-50).

source/admin/overall_status_report.md.erb

@@ -99,7 +99,7 @@ There are several fields that you should pay attention to to detect common probl
 
 #### Requests in queue
 
-Is `Requests in queue` higher than ~2 for a long time? Then it indicates that the application is either stuck or not fast enough to handle the traffic. To deal with stuck applications, please read [Dealing with common request-related problems](#dealing-with-common-request-related-problems). To handle traffic more quickly, please read the [optimization guide](<%= "/config/#{integration_mode_type}/optimization/" %>) or [scale your cluster](<%= url_for "/deploy/#{integration_mode_type}/index.html" %>).
+Is `Requests in queue` higher than ~2 for a long time? Then it indicates that the application is either stuck or not fast enough to handle the traffic. To deal with stuck applications, please read [Dealing with common request-related problems](#dealing-with-common-request-related-problems). To handle traffic more quickly, please read the [optimization guide](<%= "/config/#{integration_mode_type}/optimization/index.html" %>) or [scale your cluster](<%= url_for "/deploy/#{integration_mode_type}/index.html" %>).
 
 #### Sessions
 

source/config/reference/standalone/_index.md.erb

@@ -2001,7 +2001,7 @@ Sets the name of the [sticky sessions](#--sticky-sessions-sticky_sessions) cooki
   </tr>
 </table>
 
-Disables [turbocaching](<%= url_for "/indepth/turbocaching.html" %>).
+Disables [turbocaching](<%= url_for "/dev/index.html" %>).
 
 
 ### `--unlimited-concurrency-path` / "unlimited_concurrency_paths"

source/dev/index2.md.erb

@@ -52,7 +52,7 @@ content_for(:sidebar) { render_partial("sidebar.html", locals: locals.merge(cont
       <li><a href="<%= url_for "/config/tuning_sse_and_websockets/index.html" %>">Configuration: Tuning for Server Sent Events and WebSockets</a></li>
       <li><a href="<%= url_for "/admin/debugging_console/index.html" %>">Administration, debugging and troubleshooting: Debugging console</a></li>
       <% if language_type == :ruby %>
-        <li><a href="<%= url_for "/config/ruby/bundler.html" %>">In-depth: Bundler support</a></li>
+        <li><a href="<%= url_for "/indepth/ruby/bundler.html" %>">In-depth: Bundler support</a></li>
       <% end %>
       <% if language_type == :nodejs %>
         <li><a href="<%= url_for "/indepth/#{language_type}/reverse_port_binding.html" %>">In-depth: Reverse port binding</a></li>

source/dev/ruby/rails_integration.md.erb

@@ -117,7 +117,7 @@ If your application, or any of the libraries you use, establish any other socket
 
 Passenger -- through its Standalone mode -- is able to integrate with the `rails server` command. This integration happens through the Gemfile:
 
- 1. The Gemfile must load the `passenger` gem (or for [Passenger Enterprise](<%= url_for "/config/open_source_vs_enterprise.html" %>) users, the `passenger-enterprise-server` gem).
+ 1. The Gemfile must load the `passenger` gem (or for [Passenger Enterprise](<%= url_for "/indepth/open_source_vs_enterprise.html" %>) users, the `passenger-enterprise-server` gem).
  2. The Passenger Gemfile entry must require `phusion_passenger/rack_handler`.
 
 Here is an example Gemfile entry (for Passenger open source):

source/walkthroughs/deploy/intro.html.erb

@@ -44,7 +44,7 @@ content_for(:sidebar) { render_partial("_toc.html", locals: locals) }
   <div class="col-md-4">
     <h4>Advanced user?</h4>
     <p>
-      Simply skip the steps that you are already familiar with, or refer to our <a href="<%= url_for "/install/#{language_type}/index.html" %>">installation guides</a> which are not end-to-end, but are shorter and more focused.
+      Simply skip the steps that you are already familiar with, or refer to our <a href="<%= url_for "/install/index.html" %>">installation guides</a> which are not end-to-end, but are shorter and more focused.
     </p>
   </div>
 </div>