Pluralise table names

Author: paulbalandan

user_guide_src/source/guides/api/code/007.php

@@ -6,7 +6,7 @@
 
 class AuthorModel extends Model
 {
-    protected $table         = 'author';
+    protected $table         = 'authors';
     protected $primaryKey    = 'id';
     protected $allowedFields = ['name'];
     protected $useTimestamps = true;

user_guide_src/source/guides/api/code/008.php

@@ -6,7 +6,7 @@
 
 class BookModel extends Model
 {
-    protected $table         = 'book';
+    protected $table         = 'books';
     protected $primaryKey    = 'id';
     protected $allowedFields = ['title', 'author_id', 'year'];
     protected $useTimestamps = true;

user_guide_src/source/guides/api/code/013.php

@@ -6,7 +6,7 @@
 
 class BookModel extends Model
 {
-    protected $table         = 'book';
+    protected $table         = 'books';
     protected $allowedFields = ['title', 'author_id', 'year'];
 
     /**

user_guide_src/source/guides/api/database-setup.rst

@@ -7,12 +7,12 @@ Creating the Database and Model
     :local:
     :depth: 2
 
-In this section, we set up the data layer by creating a SQLite database table for our ``books`` resource, seeding it with sample data, and defining a model to access it. By the end, you'll have a working ``book`` table populated with example rows.
+In this section, we set up the data layer by creating a SQLite database table for our ``books`` resource, seeding it with sample data, and defining a model to access it. By the end, you'll have a working ``books`` table populated with example rows.
 
 Create the Migrations
 =====================
 
-Migrations let you version-control your database schema by defining what to apply and how to roll it back. Let's make ones for simple ``author`` and ``book`` tables.
+Migrations let you version-control your database schema by defining what to apply and how to roll it back. Let's make ones for simple ``authors`` and ``books`` tables.
 
 Run the Spark command:
 
@@ -33,7 +33,7 @@ Now, edit **app/Database/Migrations/CreateBooksTable.php** to look like this:
 
 .. literalinclude:: code/005.php
 
-This contains a foreign key reference to the ``author`` table. It lets us associate each book with an author and keep author names in one place.
+This contains a foreign key reference to the ``authors`` table. It lets us associate each book with an author and keep author names in one place.
 
 Now run the migration:
 
@@ -58,7 +58,7 @@ Edit the file at **app/Database/Seeds/BookSeeder.php**:
 
 .. literalinclude:: code/006.php
 
-This seeder first inserts authors into the ``author`` table, captures their IDs, and then uses those IDs to insert books into the ``book`` table.
+This seeder first inserts authors into the ``authors`` table, captures their IDs, and then uses those IDs to insert books into the ``books`` table.
 
 Then run the seeder:
 
@@ -71,7 +71,7 @@ You should see confirmation messages indicating the rows were inserted.
 Create the Book model
 =====================
 
-Models make database access simple and reusable by providing an object-oriented interface to your tables and a fluent query API. Let's create models for the ``author`` and ``book`` tables.
+Models make database access simple and reusable by providing an object-oriented interface to your tables and a fluent query API. Let's create models for the ``authors`` and ``books`` tables.
 
 Generate one:
 

user_guide_src/source/guides/api/first-endpoint.rst

@@ -115,4 +115,4 @@ The ``respond()`` method can return additional data:
 
 .. literalinclude:: code/003.php
 
-You now have a working endpoint tested in both the browser and cURL. In the next section, we'll create our first real database resource. You'll define a **migration**, **seeder**, and **model** for a simple ``book`` table that powers the API's CRUD endpoints.
+You now have a working endpoint tested in both the browser and cURL. In the next section, we'll create our first real database resource. You'll define a **migration**, **seeder**, and **model** for a simple ``books`` table that powers the API's CRUD endpoints.