Fix multiple H1 headings in documentation for improved search indexing

Continue fixing H1 heading issues by addressing files with multiple H1s.
Demoted duplicate H1s to H2 throughout documentation while maintaining
proper heading hierarchy (H1→H2→H3→H4).

Files changed:
- tutorial.md: Demoted 6 H1s (Table of Contents, Installation, HMR, Deployment, Going Further, Conclusion)
- rails-engine-integration.md: Changed "Github Issues" H1 to H2
- hmr-and-hot-reloading-with-the-webpack-dev-server.md: Fixed 2 H1s with proper hierarchy
- i18n.md: "Notes" H1 to H2
- react-and-redux.md: "Redux Reducers" H1 to H2
- react-router.md: "Server Rendering Using React Router V4" H1 to H2
- rspec-configuration.md: 2 H1s to H2s
- generator-details.md: "Understanding the Organization..." H1 to H2
- redux-store-api.md: "More Details" H1 to H2
- view-helpers-api.md: "More details" H1 to H2
- style.md: "Git Usage" H1 to H2

Rationale: Multiple H1s per document confuse Algolia search ranking,
screen readers, and violate accessibility standards. Each document
should have exactly one H1 as the main title.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: ihabadham

docs/advanced-topics/rails-engine-integration.md

@@ -32,7 +32,7 @@ As far as solving the assets issue, `lib/tasks/assets.rake` in `react_on_rails`
 
 Another solution would be to detach this rake task from the `rails assets:precompile` task. This can be done by adding `REACT_ON_RAILS_PRECOMPILE=false` to your environment. If you do so, then React assets will have to be bundled separately from `rails assets:precompile`.
 
-# Github Issues
+## Github Issues
 
 - [Integration with an engine #342](https://github.com/shakacode/react_on_rails/issues/342)
 - [Feature: target destination option for the install generator #459](https://github.com/shakacode/react_on_rails/issues/459)

docs/api-reference/generator-details.md

@@ -39,7 +39,7 @@ Then you may run
 
 Another good option is to create a simple test app per the [Tutorial](../getting-started/tutorial.md).
 
-# Understanding the Organization of the Generated Client Code
+## Understanding the Organization of the Generated Client Code
 
 The generated client code follows our organization scheme. Each unique set of functionality is given its own folder inside of `app/javascript/app/bundles`. This encourages modularity of _domains_.
 
@@ -51,7 +51,7 @@ Inside the generated "HelloWorld" domain you will find the following folders:
 
 You may also notice the `app/lib` folder. This is for any code that is common between bundles and therefore needs to be shared (for example, middleware).
 
-## Redux
+### Redux
 
 If you have used the `--redux` generator option, you will notice the familiar additional redux folders in addition to the aforementioned folders. The Hello World example has also been modified to use Redux.
 

docs/api-reference/redux-store-api.md

@@ -98,7 +98,7 @@ This method has the same API as the controller extension. **HOWEVER**, we recomm
 
 Place this view helper (no parameters) at the end of your shared layout so ReactOnRails will render the redux store hydration data. Since we're going to be setting up the stores in the controllers, we need to know where on the view to put the client-side rendering of this hydration data, which is a hidden div with a matching class that contains a data props. For an example, see [spec/dummy/app/views/layouts/application.html.erb](https://github.com/shakacode/react_on_rails/tree/master/spec/dummy/app/views/layouts/application.html.erb).
 
-# More Details
+## More Details
 
 - [lib/react_on_rails/controller.rb](https://github.com/shakacode/react_on_rails/tree/master/lib/react_on_rails/controller.rb) source
 - [lib/react_on_rails/helper.rb](https://github.com/shakacode/react_on_rails/tree/master/lib/react_on_rails/helper.rb) source

docs/api-reference/view-helpers-api.md

@@ -158,6 +158,6 @@ See the [React on Rails Pro Configuration](https://github.com/shakacode/react_on
 
 ---
 
-# More details
+## More details
 
 See the [lib/react_on_rails/helper.rb](https://github.com/shakacode/react_on_rails/tree/master/lib/react_on_rails/helper.rb) source.

docs/building-features/hmr-and-hot-reloading-with-the-webpack-dev-server.md

@@ -14,13 +14,13 @@ If you are **_not_** using server-side rendering (**_not_** using `prerender: tr
 then you can follow all the regular docs for using the `bin/shakapacker-dev-server`
 during development.
 
-# Server Side Rendering with the Default shakacode/shakapacker bin/shakapacker-dev-server
+## Server Side Rendering with the Default shakacode/shakapacker bin/shakapacker-dev-server
 
 If you are using server-side rendering, then you have a couple of options. The
 recommended technique is to have a different Webpack configuration for server
 rendering.
 
-## If you use the same Webpack setup for your server and client bundles
+### If you use the same Webpack setup for your server and client bundles
 
 If you do use the `webpack-dev-server` for prerendering, be sure to set the
 `config/initializers/react_on_rails.rb` setting of
@@ -40,9 +40,9 @@ If you don't configure these two to false, you'll see errors like:
 - `ReferenceError: window is not defined` (if `hmr` is true)
 - `TypeError: Cannot read property 'prototype' of undefined` (if `inline` is true)
 
-# Client-Side rendering with HMR using react-refresh-webpack-plugin
+## Client-Side rendering with HMR using react-refresh-webpack-plugin
 
-## Basic installation
+### Basic installation
 
 To enable the HMR functionality, you have to use `./bin/shakapacker-dev-server`
 

docs/building-features/i18n.md

@@ -92,7 +92,7 @@ By default, the locales are generated as JSON, but you can also generate them as
    )
    ```
 
-# Notes
+## Notes
 
 - See why using JSON can perform better compared to JS for large amounts of data [https://v8.dev/blog/cost-of-javascript-2019#json](https://v8.dev/blog/cost-of-javascript-2019#json).
 - See [Support for Rails' i18n pluralization #1000](https://github.com/shakacode/react_on_rails/issues/1000) for a discussion of issues around pluralization.

docs/building-features/react-and-redux.md

@@ -4,7 +4,7 @@
 
 See [Sharing State Between Components](https://react.dev/learn/sharing-state-between-components).
 
-# Redux Reducers
+## Redux Reducers
 
 The `helloWorld/reducers/index.jsx` example that results from running the generator with the Redux option may be slightly confusing because of its simplicity. For clarity, what follows is a more fleshed-out example of what a reducer might look like:
 

docs/building-features/react-router.md

@@ -28,7 +28,7 @@ For a fleshed out integration of React on Rails with React Router, check out [Re
 
 - [react-webpack-rails-tutorial/client/app/bundles/comments/routes/routes.jsx](https://github.com/shakacode/react-webpack-rails-tutorial/blob/master/client/app/bundles/comments/routes/routes.jsx)
 
-# Server Rendering Using React Router V4
+## Server Rendering Using React Router V4
 
 Your Render-Function may not return an object with the property `renderedHtml`. Thus, you call
 `renderToString()` and return an object with this property.

docs/building-features/rspec-configuration.md

@@ -2,7 +2,7 @@
 
 _Click [here for minitest](../building-features/minitest-configuration.md)_
 
-# If your Webpack configurations correspond to Shakapacker's default setup
+## If your Webpack configurations correspond to Shakapacker's default setup
 
 If you're able to configure your Webpack configuration to be run by having your Webpack configuration
 returned by the files in `/config/webpack`, then you have 2 options to ensure that your files are
@@ -20,7 +20,7 @@ config.build_test_command = "NODE_ENV=test RAILS_ENV=test bin/shakapacker"
 Which should you use? If you're already using the `Shakapacker` way to configure Webpack, then
 you can keep things simple and use the `Shakapacker` options.
 
-# Checking for stale assets using React on Rails
+## Checking for stale assets using React on Rails
 
 Because you will probably want to run RSpec tests that rely on compiled Webpack assets (typically, your integration/feature specs where `js: true`), you will want to ensure you don't accidentally run tests on missing or stale Webpack assets. If you did use stale Webpack assets, you will get invalid test results as your tests do not use the very latest JavaScript code.
 

docs/getting-started/tutorial.md

@@ -22,7 +22,7 @@ By the time you read this, the latest may have changed. Be sure to check the ver
 - [https://rubygems.org/gems/react_on_rails](https://rubygems.org/gems/react_on_rails)
 - [https://www.npmjs.com/package/react-on-rails](https://www.npmjs.com/package/react-on-rails)
 
-# Table of Contents
+## Table of Contents
 
 - [Installation](#installation)
   - [Setting up your environment](#setting-up-your-environment)
@@ -42,9 +42,9 @@ By the time you read this, the latest may have changed. Be sure to check the ver
     - [RubyMine performance tip](#rubymine-performance-tip)
 - [Conclusion](#conclusion)
 
-# Installation
+## Installation
 
-## Setting up your environment
+### Setting up your environment
 
 Trying out **React on Rails** is super easy, so long as you have the basic prerequisites.
 
@@ -54,7 +54,7 @@ Trying out **React on Rails** is super easy, so long as you have the basic prere
 - **yarn:** We use [yarn classic](https://classic.yarnpkg.com/) as our node package manager.
 - You need to have either [Overmind](https://github.com/DarthSim/overmind) or [Foreman](https://rubygems.org/gems/foreman) as a process manager.
 
-## Create a new Ruby on Rails App
+### Create a new Ruby on Rails App
 
 Then we need to create a fresh Rails application as follows.
 
@@ -72,7 +72,7 @@ cd test-react-on-rails
 
 Note: You can use `--database=postgresql` option to use Postgresql for the database.
 
-## Add the Shakapacker and react_on_rails gems
+### Add the Shakapacker and react_on_rails gems
 
 We recommend using the latest version of these gems. Otherwise, specify the
 exact versions of both the gem and npm packages. In other words, don't use
@@ -86,7 +86,7 @@ bundle add shakapacker --strict
 Note: The latest released React On Rails version is considered stable. Please use the latest
 version to ensure you get all the security patches and the best support.
 
-## Run the Shakapacker generator
+### Run the Shakapacker generator
 
 ```bash
 bundle exec rails shakapacker:install
@@ -100,7 +100,7 @@ git commit -am "Initial commit"
 
 Alternatively, you can use `--ignore-warnings` in the next step.
 
-## Run the React on Rails Generator
+### Run the React on Rails Generator
 
 ```bash
 rails generate react_on_rails:install
@@ -118,7 +118,7 @@ rails generate react_on_rails:install --redux
 
 If you prefer to use React Hooks instead of Redux, run the basic installer without the `--redux` flag.
 
-## Setting up your environment variables
+### Setting up your environment variables
 
 Add the following variable to your environment:
 
@@ -128,7 +128,7 @@ EXECJS_RUNTIME=Node
 
 Then run the server with one of the following options:
 
-## Running the app
+### Running the app
 
 ```bash
 ./bin/dev # For HMR
@@ -138,7 +138,7 @@ Then run the server with one of the following options:
 
 Visit [http://localhost:3000/hello_world](http://localhost:3000/hello_world) and see your **React On Rails** app running!
 
-# HMR vs. React Hot Reloading
+## HMR vs. React Hot Reloading
 
 First, check that the `hmr` and the `inline` options are `true` in your `config/shakapacker.yml` file.
 
@@ -154,7 +154,7 @@ If you want to go further with HMR, take a look at these links:
 
 React on Rails will automatically handle disabling server rendering if there is only one bundle file created by the Webpack development server by `shakapacker`.
 
-# Deployment
+## Deployment
 
 Now that you have React on Rails working locally, you're ready to deploy to production!
 
@@ -171,9 +171,9 @@ These guides cover:
 - Environment variables
 - Troubleshooting common deployment issues
 
-# Going Further
+## Going Further
 
-## Turning on Server Rendering
+### Turning on Server Rendering
 
 You can turn on server rendering by simply changing the `prerender` option to `true`:
 
@@ -217,9 +217,9 @@ For more details on server rendering, see:
 - [Client vs. Server Rendering](../core-concepts/client-vs-server-rendering.md)
 - [React Server Rendering](../core-concepts/react-server-rendering.md)
 
-## Optional Configuration
+### Optional Configuration
 
-### Moving from the Rails default `/app/javascript` to the recommended `/client` structure
+#### Moving from the Rails default `/app/javascript` to the recommended `/client` structure
 
 ShakaCode recommends that you use `/client` for your client side app. This way a non-Rails, front-end developer can be at home just by opening up the `/client` directory.
 
@@ -235,7 +235,7 @@ mv app/javascript client
 source_path: client
 ```
 
-### Custom IP & PORT setup (Cloud9 example)
+#### Custom IP & PORT setup (Cloud9 example)
 
 In case you are running some custom setup with different IP or PORT you should also edit Procfile.dev. For example, to be able to run on free Cloud9 IDE we are putting IP 0.0.0.0 and PORT 8080. The default generated file `Procfile.dev` uses `-p 3000`.
 
@@ -245,14 +245,14 @@ web: rails s -p 8080 -b 0.0.0.0
 
 Then visit https://your-shared-addr.c9users.io:8080/hello_world
 
-### RubyMine performance tip
+#### RubyMine performance tip
 
 It's super important to exclude certain directories from RubyMine or else it will slow to a crawl as it tries to parse all the npm files.
 
 - Generated files, per the settings in your `config/shakapacker.yml`, which default to `public/packs` and `public/packs-test`
 - `node_modules`
 
-# Conclusion
+## Conclusion
 
 - Browse the docs on [our documentation website](https://www.shakacode.com/react-on-rails/docs/)