Update Turbolinks doc and release notes

Author: alexeyr

docs/rails/turbolinks.md

@@ -84,7 +84,7 @@ Async script loading can be done like this:
   <%= javascript_include_tag 'application', async: Rails.env.production? %>
 ```
 
-If you use `document.addEventListener("turbolinks:load", function() {...});` somewhere in your code, you will notice that Turbolinks 5 does not fire `turbolinks:load` on initial page load. A quick workaround is to use `defer` instead of `async`:
+If you use `document.addEventListener("turbolinks:load", function() {...});` somewhere in your code, you will notice that Turbolinks 5 does not fire `turbolinks:load` on initial page load. A quick workaround for React on Rails <15 is to use `defer` instead of `async`:
 
 ```erb
   <%= javascript_include_tag 'application', defer: Rails.env.production? %>
@@ -100,6 +100,8 @@ document.addEventListener('turbolinks:load', function () {
 });
 ```
 
+React on Rails 15 fixes both issues, so if you still have the listener it can be removed (and should be as `reactOnRailsPageLoaded()` is now async).
+
 ## Troubleshooting
 
 To turn on tracing of Turbolinks events, put this in your registration file, where you register your components.

docs/release-notes/15.0.0.md

@@ -30,22 +30,25 @@ Major improvements to component and store hydration:
   - The previous need for deferring scripts to prevent race conditions has been eliminated due to improved hydration handling. Making scripts not defer is critical to execute the hydration scripts early before the page is fully loaded.
   - The `force_load` configuration makes `react-on-rails` hydrate components immediately as soon as their server-rendered HTML reaches the client, without waiting for the full page load.
   - If you want to keep the previous behavior, you can set `defer_generated_component_packs: true` or `force_load: false` in your `config/initializers/react_on_rails.rb` file.
-    - To do that for only some components, you can call `force_load: false` in the `react_component` helper or `force_load` configuration.
-  - Redux store now supports `force_load` option, and uses `config.force_load` value as the default value. Which means that the Redux store will hydrate immediately as soon as its server-side data reaches the client. You can override this behavior for individual Redux stores by calling the `redux_store` helper with `force_load: false`.
+    - You can also keep it for individual components by passing `force_load: false` to `react_component` or `stream_react_component`.
+  - Redux store now supports `force_load` option, which defaults to `config.force_load` (and so to `true` if that isn't set). If `true`, the Redux store will hydrate immediately as soon as its server-side data reaches the client.
+    - You can override this behavior for individual Redux stores by calling the `redux_store` helper with `force_load: false`, same as `react_component`.
 
 - `ReactOnRails.reactOnRailsPageLoaded()` is now an async function:
 
-  - If you are manually calling this function to ensure components are hydrated (e.g. with async script loading), you must now await the promise it returns:
+  - If you manually call this function to ensure components are hydrated (e.g., with async script loading), you must now await the promise it returns:
 
-  ```js
-  // Before
-  ReactOnRails.reactOnRailsPageLoaded();
-  // Code expecting all components to be hydrated
+    ```js
+    // Before
+    ReactOnRails.reactOnRailsPageLoaded();
+    // Code expecting all components to be hydrated
 
-  // After
-  await ReactOnRails.reactOnRailsPageLoaded();
-  // Code expecting all components to be hydrated
-  ```
+    // After
+    await ReactOnRails.reactOnRailsPageLoaded();
+    // Code expecting all components to be hydrated
+    ```
+
+  - If you call it in a `turbolinks:load` listener to work around the issue documented in [Turbolinks](../rails/turbolinks.md#async-script-loading), the listener can be safely removed.
 
 ## Store Dependencies for Components