Fix broken links

Author: JonRowe

features/controller_specs/README.md

@@ -19,22 +19,22 @@ To specify outcomes, you can use:
 - standard test/unit assertions (`assert_equal 200, response.status`)
 - rails assertions (`assert_response 200`)
 - rails-specific matchers:
-  - [`render_template`](../matchers/render-template-matcher)
+  - [`render_template`](./matchers/render-template-matcher)
 
     ```ruby
     expect(response).to render_template(:new)   # wraps assert_template
     ```
-  - [`redirect_to`](../matchers/redirect-to-matcher)
+  - [`redirect_to`](./matchers/redirect-to-matcher)
 
     ```ruby
     expect(response).to redirect_to(location)   # wraps assert_redirected_to
     ```
-  - [`have_http_status`](../matchers/have-http-status-matcher)
+  - [`have_http_status`](./matchers/have-http-status-matcher)
 
     ```ruby
     expect(response).to have_http_status(:created)
     ```
-  - [`be_a_new`](../matchers/be-a-new-matcher)
+  - [`be_a_new`](./matchers/new-record-matcher)
 
     ```ruby
     expect(assigns(:widget)).to be_a_new(Widget)
@@ -60,12 +60,12 @@ To specify outcomes, you can use:
 ## Views
 
 * by default, views are not rendered. See
-  [views are stubbed by default](controller-specs/views-are-stubbed-by-default) and
-  [render_views](controller-specs/render-views) for details.
+  [views are stubbed by default](./controller-specs/isolation-from-views) and
+  [render_views](./controller-specs/render-views) for details.
 
 ## Headers
 
-We encourage you to use [request specs](https://relishapp.com/rspec/rspec-rails/docs/request-specs/request-spec) if you want to set headers in your call. If you still want to use controller specs with custom http headers you can use `request.headers`:
+We encourage you to use [request specs](../request-specs/request-spec) if you want to set headers in your call. If you still want to use controller specs with custom http headers you can use `request.headers`:
 
     require "rails_helper"
 

features/directory_structure.feature

@@ -54,7 +54,7 @@ Feature: The directory structure
   **Note:** Standard RSpec specs do not require any additional metadata by
   default.
 
-  Check out the [`rspec-core`](../../latest/rspec-core) documentation on [using metadata](../../latest/rspec-core/metadata) for more details.
+  Check out the [`rspec-core`](../../3-12/rspec-core) documentation on [using metadata](../../3-12/rspec-core/metadata) for more details.
 
   **Automatically Adding Metadata**
 

features/matchers/render_template_matcher.feature

@@ -2,7 +2,7 @@ Feature: `render_template` matcher
 
   The `render_template` matcher is used to specify that a request renders a
   given template or layout.  It delegates to
-  [`assert_template`](https://api.rubyonrails.org/classes/ActionController/TemplateAssertions.html#method-i-assert_template)
+  [`assert_template`](https://api.rubyonrails.org/v5.2/classes/ActionController/TemplateAssertions.html#method-i-assert_template)
 
   It is available in controller specs (spec/controllers) and request
   specs (spec/requests).

features/upgrade/README.md

@@ -16,4 +16,4 @@ RSpec Rails 4 is a major version under semantic versioning, it allowed us to cha
 
 If you are using Rails 4.2 you can use RSpec Rails 4, but note that support for it is not maintained, we consider this a breaking change hence the version change, and you must be on Ruby 2.2 as a minimum.
 
-If you are upgrading from an earlier version of RSpec Rails, please consult [the upgrading 2.x to 3.x guide](https://relishapp.com/rspec/rspec-rails/v/3-9/docs/upgrade).
+If you are upgrading from an earlier version of RSpec Rails, please consult [the upgrading 2.x to 3.x guide](https://web.archive.org/web/20221206041517/https://relishapp.com/rspec/rspec-rails/v/3-9/docs/upgrade).