[Seaography] Docs

Author: tyt2y3

Seaography/docs/01-index.md

@@ -37,5 +37,5 @@
 2. [Schema Restrictions](06-access-control/02-schema-restrictions.md)
 3. [Entity / Field Guards](06-access-control/03-guards.md)
 4. [Fine-grained Filters](06-access-control/04-filters.md)
-5. [Role Based Access Control](06-access-control/05-RBAC.md)
+5. [Role Based Access Control](06-access-control/05-rbac.md)
 6. [Considerations](06-access-control/06-considerations.md)

Seaography/docs/04-custom-endpoints/03-custom-mutation.md

@@ -69,7 +69,11 @@ pub struct Coupon {
 }
 ```
 
-Then we can define the mutation endpoint:
+Then we can define the mutation endpoint. The business logic is:
+
+1. Look up the specifc customer and film
+2. Find if there is inventory in store. If not, return error
+3. Create a new rental record and remove the item from inventory
 
 ```rust
 #[CustomFields]
@@ -86,7 +90,7 @@ impl Operations {
         //  ⬆ create a transaction to make operation atomic
 
         let customer = Customer::find_by_name(rental_request.customer, &txn).await?;
-        let film = Film::find_by_name(rental_request.film, &txn).await?;
+        let film = Film::find_by_title(rental_request.film, &txn).await?;
         //  ⬆ helper methods to find the corresponding customer and film
 
         //  ⬇ find if there is inventory in current store

Seaography/docs/06-access-control/02-schema-restrictions.md

@@ -37,7 +37,7 @@ pub enum RelatedEntity {
 
 ## No mutation
 
-You can also register entities without mutation if you intend to implement all mutations with custom endpoints:
+You can also register entities without mutation if you intend to implement all mutations with custom operations:
 
 ```rust
 seaography::register_entity!(builder, actor, mutation: false);
@@ -58,6 +58,6 @@ pub struct Model {
 }
 ```
 
-This column will still be usable in other parts of the application, for example in custom endpoints. But it will not be visible to clients.
+This column will still be usable in other parts of the application, for example in custom operations. But it will not be visible to clients.
 
 If you remove this field from the struct, then this column will not be visible to the entire application.

Seaography/docs/06-access-control/05-rbac.md.bak renamed to Seaography/docs/06-access-control/05-rbac.md

@@ -25,7 +25,7 @@ Combining RBAC with Entity Filters, it lets you implement rules such as "admins
 For **end‑user facing applications**, resources often have an *owner* (e.g. a user's own posts, orders, or profile).  
 In these cases, you can enforce access by:
 - Adding **Filters** to queries so users only see their own data.
-- Using **Guards** on mutations to ensure a user can only read, update or delete resources they own.
+- Using **Guards** on queries / mutations to ensure a user can only read, update or delete resources they own.
 
 This pattern is common in SaaS where each user should only interact with their own records.