diff --git a/help/api-tables.html b/help/api-tables.html
index b101f18..175abc9 100644
--- a/help/api-tables.html
+++ b/help/api-tables.html
@@ -50,7 +50,9 @@ In general, having 'title' and 'help' at the table level doesn't make a lot of s
$data['foo']['table']['group'] = t('Foo');
-
Base table
+The other items in the 'table' section are described in the following sections.
+
+'base': Base table
If your table is a base table -- meaning it can be the primary, central table for a View to use, you can declare it to be a base table. This primarily provides UI information so that it can be selected.
For example:
@@ -63,7 +65,7 @@ For example:
);
-The following tags are available in the
+The following items are available in the base section:
- field
- The primary key field for this table. For Views to treat any table as a base table, it must have a primary field. For node this is the 'nid', for users this is the 'uid', etc. Without a single primary key field (i.e. not a composite key), Views will not be able to utilize the table as a base table. If your table does not have a primary key field, it is not too difficult to just add a serial field to it, usually.
@@ -92,7 +94,7 @@ Then when you are describing the external database in your base table you would
-Linking your table to existing base tables
+'join': Linking your table to existing base tables
For Views to use your table, it has to either be a base table, or know how to link to an existing base table. Or sometimes both. Views uses this information to create a path to the base table; when the table is added to the query, Views will walk along this path, adding all tables required into the query.