From 22b6ff764dd985a02b031988832bbc6d6a9d2c57 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Steve=20Ch=C3=A1vez?= <stevechavezast@gmail.com>
Date: Fri, 18 Oct 2019 11:03:32 -0500
Subject: [PATCH] Credit howtos/tuts authors (#264)

---
 how-tos/casting-type-to-custom-json.rst         | 4 +++-
 how-tos/embedding-table-from-another-schema.rst | 2 ++
 tutorials/tut0.rst                              | 2 ++
 tutorials/tut1.rst                              | 2 ++
 4 files changed, 9 insertions(+), 1 deletion(-)

diff --git a/how-tos/casting-type-to-custom-json.rst b/how-tos/casting-type-to-custom-json.rst
index f9d13afa7..b2b25128d 100644
--- a/how-tos/casting-type-to-custom-json.rst
+++ b/how-tos/casting-type-to-custom-json.rst
@@ -1,6 +1,8 @@
 Casting a type to a custom JSON object
 ======================================
 
+:author: `steve-chavez <https://github.com/steve-chavez>`_
+
 While using PostgREST you might have noticed that certain PostgreSQL types translate to JSON strings when you would
 have expected a JSON object or array. For example, let's see the case of `range types <https://www.postgresql.org/docs/11/rangetypes.html>`_.
 
@@ -82,7 +84,7 @@ You can use the same idea for creating custom CASTs for different types.
 
 .. note::
 
-   If you don't want to modify CASTs for built-in types, an option would be to `create a custom type <https://www.postgresql.org/docs/current/sql-createtype.html>`_ 
+   If you don't want to modify CASTs for built-in types, an option would be to `create a custom type <https://www.postgresql.org/docs/current/sql-createtype.html>`_
    for your own ``tsrange`` and add its own CAST.
 
    .. code-block:: postgres
diff --git a/how-tos/embedding-table-from-another-schema.rst b/how-tos/embedding-table-from-another-schema.rst
index 60265dd40..118d630d1 100644
--- a/how-tos/embedding-table-from-another-schema.rst
+++ b/how-tos/embedding-table-from-another-schema.rst
@@ -1,6 +1,8 @@
 Embedding a table from another schema
 =====================================
 
+:author: `steve-chavez <https://github.com/steve-chavez>`_
+
 Suppose you have a **people** table in the ``public`` schema and this schema is exposed through PostgREST's :ref:`db-schema`.
 
 .. code-block:: postgres
diff --git a/tutorials/tut0.rst b/tutorials/tut0.rst
index e061b4761..038b92f6f 100644
--- a/tutorials/tut0.rst
+++ b/tutorials/tut0.rst
@@ -3,6 +3,8 @@
 Tutorial 0 - Get it Running
 ===========================
 
+:author: `begriffs <https://github.com/begriffs>`_
+
 Welcome to PostgREST! In this pre-tutorial we're going to get things running so you can create your first simple API.
 
 PostgREST is a standalone web server which turns a PostgreSQL database into a RESTful API. It serves an API that is customized based on the structure of the underlying database.
diff --git a/tutorials/tut1.rst b/tutorials/tut1.rst
index 71c288d11..e9fe78f54 100644
--- a/tutorials/tut1.rst
+++ b/tutorials/tut1.rst
@@ -3,6 +3,8 @@
 Tutorial 1 - The Golden Key
 ===========================
 
+:author: `begriffs <https://github.com/begriffs>`_
+
 In :ref:`tut0` we created a read-only API with a single endpoint to list todos. There are many directions we can go to make this API more interesting, but one good place to start would be allowing some users to change data in addition to reading it.
 
 Step 1. Add a Trusted User