Fix some typos & formatting in operations-api/databases-and-tables.md (#221)

Just some small cleanups and fixes for some issues I noticed

Author: cap10morgan

docs/developers/operations-api/databases-and-tables.md

@@ -2,9 +2,9 @@
 
 ## Describe All
 
-Returns the definitions of all databases and tables within the database. Record counts about 5000 records are estimated, as determining the exact count can be expensive. When the record count is estimated, this is indicated by the inclusion of a confidence interval of `estimated_record_range`. If you need the exact count, you can include an `"exact_count": true` in the operation, but be aware that this requires a full table scan (may be expensive).
+Returns the definitions of all databases and tables within the database. Record counts above 5000 records are estimated, as determining the exact count can be expensive. When the record count is estimated, this is indicated by the inclusion of a confidence interval of `estimated_record_range`. If you need the exact count, you can include an `"exact_count": true` in the operation, but be aware that this requires a full table scan (may be expensive).
 
-- operation _(required)_ - must always be `describe_all`
+- `operation` _(required)_ - must always be `describe_all`
 
 ### Body
 
@@ -59,8 +59,8 @@ Returns the definitions of all databases and tables within the database. Record
 
 Returns the definitions of all tables within the specified database.
 
-- operation _(required)_ - must always be `describe_database`
-- database _(optional)_ - database where the table you wish to describe lives. The default is `data`
+- `operation` _(required)_ - must always be `describe_database`
+- `database` _(optional)_ - database where the table you wish to describe lives. The default is `data`
 
 ### Body
 
@@ -114,9 +114,9 @@ Returns the definitions of all tables within the specified database.
 
 Returns the definition of the specified table.
 
-- operation _(required)_ - must always be `describe_table`
-- table _(required)_ - table you wish to describe
-- database _(optional)_ - database where the table you wish to describe lives. The default is `data`
+- `operation` _(required)_ - must always be `describe_table`
+- `table` _(required)_ - table you wish to describe
+- `database` _(optional)_ - database where the table you wish to describe lives. The default is `data`
 
 ### Body
 
@@ -170,8 +170,8 @@ Create a new database.
 
 _Operation is restricted to super_user roles only_
 
-- operation _(required)_ - must always be `create_database`
-- database _(optional)_ - name of the database you are creating. The default is `data`
+- `operation` _(required)_ - must always be `create_database`
+- `database` _(optional)_ - name of the database you are creating. The default is `data`
 
 ### Body
 
@@ -198,9 +198,9 @@ Drop an existing database. NOTE: Dropping a database will delete all tables and
 
 _Operation is restricted to super_user roles only_
 
-- operation _(required)_ - this should always be `drop_database`
-- database _(required)_ - name of the database you are dropping
-- replicated _(optional)_ - if true, Harper will replicate the component to all nodes in the cluster. Must be a boolean.
+- `operation` _(required)_ - this should always be `drop_database`
+- `database` _(required)_ - name of the database you are dropping
+- `replicated` _(optional)_ - if true, Harper will replicate the component to all nodes in the cluster. Must be a boolean.
 
 ### Body
 
@@ -227,15 +227,15 @@ Create a new table within a database.
 
 _Operation is restricted to super_user roles only_
 
-- operation _(required)_ - must always be `create_table`
-- database _(optional)_ - name of the database where you want your table to live. If the database does not exist, it will be created. If the `database` property is not provided it will default to `data`.
-- table _(required)_ - name of the table you are creating
-- primary*key *(required)\_ - primary key for the table
-- attributes _(optional)_ - an array of attributes that specifies the schema for the table, that is the set of attributes for the table. When attributes are supplied the table will not be considered a "dynamic schema" table, and attributes will not be auto-added when records with new properties are inserted. Each attribute is specified as:
-  - name _(required)_ - the name of the attribute
-  - indexed _(optional)_ - indicates if the attribute should be indexed
-  - type _(optional)_ - specifies the data type of the attribute (can be String, Int, Float, Date, ID, Any)
-- expiration _(optional)_ - specifies the time-to-live or expiration of records in the table before they are evicted (records are not evicted on any timer if not specified). This is specified in seconds.
+- `operation` _(required)_ - must always be `create_table`
+- `database` _(optional)_ - name of the database where you want your table to live. If the database does not exist, it will be created. If the `database` property is not provided it will default to `data`.
+- `table` _(required)_ - name of the table you are creating
+- `primary_key` _(required)_ - primary key for the table
+- `attributes` _(optional)_ - an array of attributes that specifies the schema for the table, that is the set of attributes for the table. When attributes are supplied the table will not be considered a "dynamic schema" table, and attributes will not be auto-added when records with new properties are inserted. Each attribute is specified as:
+  - `name` _(required)_ - the name of the attribute
+  - `indexed` _(optional)_ - indicates if the attribute should be indexed
+  - `type` _(optional)_ - specifies the data type of the attribute (can be String, Int, Float, Date, ID, Any)
+- `expiration` _(optional)_ - specifies the time-to-live or expiration of records in the table before they are evicted (records are not evicted on any timer if not specified). This is specified in seconds.
 
 ### Body
 
@@ -264,10 +264,10 @@ Drop an existing database table. NOTE: Dropping a table will delete all associat
 
 _Operation is restricted to super_user roles only_
 
-- operation _(required)_ - this should always be `drop_table`
-- database _(optional)_ - database where the table you are dropping lives. The default is `data`
-- table _(required)_ - name of the table you are dropping
-- replicated _(optional)_ - if true, Harper will replicate the component to all nodes in the cluster. Must be a boolean.
+- `operation` _(required)_ - this should always be `drop_table`
+- `database` _(optional)_ - database where the table you are dropping lives. The default is `data`
+- `table` _(required)_ - name of the table you are dropping
+- `replicated` _(optional)_ - if true, Harper will replicate the component to all nodes in the cluster. Must be a boolean.
 
 ### Body
 
@@ -295,10 +295,10 @@ Create a new attribute within the specified table. **The create_attribute operat
 
 _Note: Harper will automatically create new attributes on insert and update if they do not already exist within the database._
 
-- operation _(required)_ - must always be `create_attribute`
-- database _(optional)_ - name of the database of the table you want to add your attribute. The default is `data`
-- table _(required)_ - name of the table where you want to add your attribute to live
-- attribute _(required)_ - name for the attribute
+- `operation` _(required)_ - must always be `create_attribute`
+- `database` _(optional)_ - name of the database of the table you want to add your attribute. The default is `data`
+- `table` _(required)_ - name of the table where you want to add your attribute to live
+- `attribute` _(required)_ - name for the attribute
 
 ### Body
 
@@ -329,10 +329,10 @@ Drop an existing attribute from the specified table. NOTE: Dropping an attribute
 
 _Operation is restricted to super_user roles only_
 
-- operation _(required)_ - this should always be `drop_attribute`
-- database _(optional)_ - database where the table you are dropping lives. The default is `data`
-- table _(required)_ - table where the attribute you are dropping lives
-- attribute _(required)_ - attribute that you intend to drop
+- `operation` _(required)_ - this should always be `drop_attribute`
+- `database` _(optional)_ - database where the table you are dropping lives. The default is `data`
+- `table` _(required)_ - table where the attribute you are dropping lives
+- `attribute` _(required)_ - attribute that you intend to drop
 
 ### Body
 
@@ -363,10 +363,10 @@ It is important to note that trying to copy a database file that is in use (Harp
 
 _Operation is restricted to super_user roles only_
 
-- operation _(required)_ - this should always be `get_backup`
-- database _(required)_ - this is the database that will be snapshotted and returned
-- table _(optional)_ - this will specify a specific table to backup
-- tables _(optional)_ - this will specify a specific set of tables to backup
+- `operation` _(required)_ - this should always be `get_backup`
+- `database` _(required)_ - this is the database that will be snapshotted and returned
+- `table` _(optional)_ - this will specify a specific table to backup
+- `tables` _(optional)_ - this will specify a specific set of tables to backup
 
 ### Body