[6.x] Documentation Changes for Blueprints, Index, and Readme (#411)

* Added Note to call attention to the accessor being defined as a public function, which differs from the Laravel docs example.

* Changed products to product in the example to reflect the singular nature of the handle for other resources used in the documentation.

* Changed products to product in the example to reflect the singular nature of the handle for other resources used in the documentation.

* Adjust note

---------

Co-authored-by: Duncan McClean <duncan@duncanmcclean.com>

Author: mefenlon

README.md

@@ -49,10 +49,10 @@ return [
 In addition to front-end routing, you may also use Runway's tag to loop through your models and display the results. The tag supports filtering, using Eloquent scopes and sorting.
 
 ```antlers
-{{ runway:products }}
+{{ runway:product }}
     <h2>{{ name }}</h2>
     <p>Price: {{ price }}</p>
-{{ /runway:products }}
+{{ /runway:product }}
 ```
 
 -   [Review documentation](https://runway.duncanmcclean.com/templating)

docs/blueprints.md

@@ -141,3 +141,7 @@ public function fullName(): Attribute
 Then, in your user blueprint, you'd set the field's visibility to "Computed":
 
 ![Field's visibility set to computed](/img/runway/field-visibility-computed.png)
+
+:::note Note!
+It's worth noting, Runway requires any accessors to be `public` functions, otherwise the attributes won't be augmentable.
+:::

docs/index.md

@@ -32,10 +32,10 @@ return [
 In addition to front-end routing, you may also use Runway's tag to loop through your models and display the results. The tag supports filtering, using Eloquent scopes and sorting.
 
 ```antlers
-{{ runway:products }}
+{{ runway:product }}
     <h2>{{ name }}</h2>
     <p>Price: {{ price }}</p>
-{{ /runway:products }}
+{{ /runway:product }}
 ```
 
 -   [Review documentation](https://runway.duncanmcclean.com/templating)