Update docss headings

tonysm · tonysm · commit d781668bc12a · 2025-08-31T12:56:49.000-03:00
diff --git a/docs/helpers.md b/docs/helpers.md
@@ -11,7 +11,7 @@ Turbo Laravel has a set of Blade Directives, Components, helper functions, and r
 
 ## Blade Directives
 
-### The `@domid()` Blade Directive
+### The DOM ID Blade Directive
 
 Since Turbo relies a lot on DOM IDs, the package offers a helper to generate unique DOM IDs based on your models. You may use the `@domid` Blade Directive in your Blade views like so:
 
@@ -33,7 +33,7 @@ Which will generate a `comments_post_123` DOM ID, assuming your Post model has a
 
 ## Blade Components
 
-### The `<x-turbo::frame>` Blade Component
+### The Turbo Frame Blade Component
 
 You may also prefer using the `<x-turbo::frame>` Blade component that ships with the package. This way, you don't need to worry about using the `@domid()` helper for your Turbo Frame:
 
@@ -53,7 +53,7 @@ To the `:id` prop, you may pass a string, which will be used as-is as the DOM ID
 
 Additionally, you may also pass along any prop that is supported by the Turbo Frame custom Element to the `<x-turbo::frame>` Blade component, like `target`, `src`, or `loading`. These are the listed attributes, but any other attribute will also be forwarded to the `<turbo-frame>` tag that will be rendered by the `<x-turbo::frame>` component. For a full list of what's possible to do with Turbo Frames, see the [documentation](https://turbo.hotwired.dev/handbook/frames).
 
-### The `<x-turbo::stream>` Blade Component
+### The Turbo Stream Blade Component
 
 If you're rendering a Turbo Stream inside a your Blade files, you may use the `<x-turbo::stream>` helper:
 
@@ -65,7 +65,7 @@ If you're rendering a Turbo Stream inside a your Blade files, you may use the `<
 
 Just like in the Turbo Frames' `:id` prop, the `:target` prop of the Turbo Stream component accepts a string, a model instance, or an array to resolve the DOM ID using the `dom_id()` function.
 
-### The `<x-turbo::refresh-method method="morph" />` Blade Component
+### The Refresh Method Blade Component
 
 We can configure which update method Turbo should so to update the document:
 
@@ -86,7 +86,7 @@ The output would be:
 <meta name="turbo-refresh-method" content="morph">
 ```
 
-### The `<x-turbo::refresh-scroll scroll="preserve" />` Blade Component
+### The Refresh Scroll Behavior Blade Component
 
 You can also configure the scroll behavior on Turbo:
 
@@ -107,7 +107,7 @@ The output would be:
 <meta name="turbo-refresh-scroll" content="preserve">
 ```
 
-### The `<x-turbo::refreshes-with>` Blade Component
+### The Refresh Behaviors Blade Component
 
 You may configure both the refresh method and scroll behavior using the `<x-turbo::refreshes-with />` component in your main layout's `<head>` tag or on specific pages to configure how Turbo should update the page. Here's an example:
 
@@ -122,7 +122,7 @@ This will render two HTML `<meta>` tags:
 <meta name="turbo-refresh-scroll" content="preserve">
 ```
 
-### The `<x-turbo::exempts-page-from-cache />` Blade Component
+### The Page Cache Exemption Blade Component
 
 This component may be added to any page you don't want Turbo to keep a cache in the page cache. Example:
 
@@ -136,7 +136,7 @@ It will render the HTML `<meta>` tag:
 <meta name="turbo-cache-control" content="no-cache">
 ```
 
-### The `<x-turbo::exempts-page-from-preview />` Blade Component
+### The Page Preview Exemption Blade Component
 
 This component may be added to any page you don't want Turbo to show as a preview on regular navigation visits. No-preview pages will only be used in restoration visits (when you use the browser's back or forward buttons, or when when moving backward in the navigation stack). Example:
 
@@ -150,7 +150,7 @@ It will render the HTML `<meta>` tag:
 <meta name="turbo-cache-control" content="no-preview">
 ```
 
-### The `<x-turbo::page-requires-reload />` Blade Component
+### The Page Reload Blade Component
 
 This component may be added to any page you want Turbo to reload. This will break out of Turbo Frame navigations. May be used at a login screen, for instance. Example:
 
@@ -168,7 +168,7 @@ It will render the HTML `<meta>` tag:
 
 The package ships with a set of helper functions. These functions are all namespaced under `HotwiredLaravel\\TurboLaravel\\` but we also add them globally for convenience, so you may use them directly without the `use` statements (this is useful in contexts like Blade views, for instance).
 
-### The `dom_id()`
+### The DOM ID Helper Function
 
 The mentioned namespaced `dom_id()` helper function may also be used from anywhere in your application, like so:
 
@@ -182,7 +182,7 @@ When a new instance of a model is passed to any of these DOM ID helpers, since i
 
 These helpers strip out the model's FQCN (see [config/turbo-laravel.php](https://github.com/hotwired-laravel/turbo-laravel/blob/main/config/turbo-laravel.php) if you use an unconventional location for your models).
 
-### The `dom_class()`
+### The DOM CSS Class Helper Function
 
 The `dom_class()` helper function may be used from anywhere in your application, like so:
 
@@ -202,7 +202,7 @@ dom_class($comment, 'reactions_list');
 
 This will generate a DOM class of `reactions_list_comment`.
 
-### The `turbo_stream()`
+### The Turbo Stream Helper Function
 
 You may generate Turbo Streams using the `Response::turboStream()` macro, but you may also do so using the `turbo_stream()` helper function:
 
@@ -214,7 +214,7 @@ turbo_stream()->append($comment);
 
 Both the `Response::turboStream()` and the `turbo_stream()` function work the same way. The `turbo_stream()` function may be easier to use.
 
-### The `turbo_stream_view()`
+### The Turbo Stream View Helper Function
 
 You may combo Turbo Streams using the `turbo_stream([])` function passing an array, but you may prefer to create a separate Blade view with all the Turbo Streams, this way you may also use template extensions and everything else Blade offers:
 
@@ -228,13 +228,13 @@ return turbo_stream_view('comments.turbo.created', [
 
 ## Request & Response Macros
 
-### The `request()->wantsTurboStream()` macro
+### Detect If Request Accepts Turbo Streams
 
 The `request()->wantsTurboStream()` macro added to the request class will check if the request accepts Turbo Stream and return `true` or `false` accordingly.
 
 Turbo will add a `Accept: text/vnd.turbo-stream.html, ...` header to the requests. That's how we can detect if the request came from a client using Turbo.
 
-### The `request()->wasFromTurboFrame()` macro
+### Detect If Request Was Made From Turbo Frame
 
 The `request()->wasFromTurboFrame()` macro added to the request class will check if the request was made from a Turbo Frame. When used with no parameters, it returns `true` if the request has a `Turbo-Frame` header, no matter which specific Turbo Frame.
 
@@ -246,16 +246,16 @@ if (request()->wasFromTurboFrame(dom_id($post, 'create_comment'))) {
 }
 ```
 
-### The `request()->wasFromHotwireNative()` macro
+### Detect If Request Was Made From Hotwire Native Client
 
 The `request()->wasFromHotwireNative()` macro added to the request class will check if the request came from a Hotwire Native client and returns `true` or `false` accordingly.
 
 Hotwire Native clients are encouraged to override the `User-Agent` header in the WebViews to mention the words `Hotwire Native` on them. This is what this macro uses to detect if it came from a Hotwire Native client.
 
-### The `response()->turboStream()` macro
+### Turbo Stream Response Macro
 
 The `response()->turboStream()` macro works similarly to the `turbo_stream()` function above. It was only added to the response for convenience.
 
-### The `response()->turboStreamView()` macro
+### The Turbo Stream View Response Macro
 
 The `response()->turboStreamView()` macro works similarly to the `turbo_stream_view()` function above. It was only added to the response for convenience.
diff --git a/docs/turbo-frames.md b/docs/turbo-frames.md
@@ -39,7 +39,7 @@ Any other attribute passed to the Blade Component will get forwarded to the unde
 
 This will work for any other attribute you want to forward to the underlying component.
 
-## The `request()->wasFromTurboFrame()` Macro
+## Detecting Turbo Frames Requests
 
 You may want to detect if a request came from a Turbo Frame in the backend. You may use the `wasFromTurboFrame()` method for that:
 
