Merge pull request #1733 from girder/update-doc

Update some documentation

girder_annotation/docs/plottable.rst

@@ -66,7 +66,7 @@ For instance, each of the following has two separate keys with plottable data (s
 |                           |   }                                          |
 +---------------------------+----------------------------------------------+
 
-For plottable data in the ``meta`` key of a folder, (a) if the name of the most nested key matches the Python regular expression ``r'(?i)(item|image)_(id|name)$'``, then the value of that key will attempt to be resolved to the name or Girder _id of a item within the folder.  This will only match items that are included (the ``adjacentItems`` flag affects the results).  If a matching item is found, the item's canonical ``name`` and ``_id`` are used rather than the specified value.  (b) if the name of the key matches the Python regular expression ``r'(?i)(low|min|high|max)(_|)(x|y)'``, the value is assumed to be a coordinate of an image bounding box.  This can be used by clients to show a portion of the image associated with the plottable record.
+For plottable data in the ``meta`` key of a folder, (a) if the name of the most nested key matches the Python regular expression ``r'(?i)(item|image)_(id|name)$'``, then the value of that key will attempt to be resolved to the name or Girder _id of a item within the folder.  This will only match items that are included (the ``adjacentItems`` flag affects the results).  If a matching item is found, the item's canonical ``name`` and ``_id`` are used rather than the specified value.  (b) if the name of the key matches the Python regular expression ``r'(?i)((low|min|high|max)(_|)(x|y)|(^(x|y)(1|2)$))'``, the value is assumed to be a coordinate of an image bounding box.  This can be used by clients to show a portion of the image associated with the plottable record.
 
 After plottable data is gathered, columns of available data are summarized.  Each column contains: