update ASL reference docs (#231)

Fix some known issues and expand on some of the operators.

Author: brharrington

docs/api/graph/axis-bounds.md

@@ -74,7 +74,7 @@ Note the `&l=0` and `&u=60e3` parameters.
 /api/v1/graph?e=2012-01-01T09:00&s=e-1d&tz=UTC&l=0&u=60e3&q=name,sps,:eq,nf.cluster,(,nccp-xbox,nccp-silverlight,),:in,:and,:sum,(,nf.cluster,),:by
 @@@
 
-!!! Note 
+!!! Note
     It is possible to define the boundaries beyond the range of the data source
     so that a graph appears empty.
 

docs/api/graph/basics.md

@@ -28,7 +28,7 @@ Putting it all together:
 The resulting [PNG] plot displays time along the X axis, automatically scaled to the proper
 time range. The Y [axis labels] are scaled using metric prefixes to show the measured value.
 A [legend] is displayed under the plot with the name(s) of the expression results and a set
-of statistics computed on the plotted data for the time window. The small text at the very 
+of statistics computed on the plotted data for the time window. The small text at the very
 bottom reflect query parameters and step size along with some processing statistics.
 
 [PNG]: outputs.md
@@ -88,8 +88,8 @@ Example that [negates](../../asl/ref/neg.md) the value of a line:
 /api/v1/graph?e=2012-01-01T00:00&q=name,sps,:eq,:neg&s=e-2d
 @@@
 
-Example that [negates](../../asl/ref/neg.md) and then applies 
-[absolute value](../../asl/ref/abs.md) to get the original value back (since all values were 
+Example that [negates](../../asl/ref/neg.md) and then applies
+[absolute value](../../asl/ref/abs.md) to get the original value back (since all values were
 positive in the input):
 
 @@@ atlas-uri { hilite=:abs }
@@ -102,7 +102,7 @@ positive in the input):
 
 ## Binary Operations
 
-Lines can be combined using binary math operators such as [add](../../asl/ref/add.md) or 
+Lines can be combined using binary math operators such as [add](../../asl/ref/add.md) or
 [multiply](../../asl/ref/mul.md). Example using [divide](../../asl/ref/div.md):
 
 @@@ atlas-uri { hilite=:div }

docs/api/graph/color-palettes.md

@@ -135,9 +135,9 @@ Shades of red.
 
 ## Custom
 
-A custom color palette can be provided for a graph by using a list of  comma separated 
-[hex color](../../asl/ref/color.md) values following the ASL list format `(,HEX,HEX,HEX,)`. 
-This is mainly used to customize the colors for the result of a group by where you 
+A custom color palette can be provided for a graph by using a list of  comma separated
+[hex color](../../asl/ref/color.md) values following the ASL list format `(,HEX,HEX,HEX,)`.
+This is mainly used to customize the colors for the result of a group by where you
 cannot set the color for each line using the list.
 
 @@@ atlas-uri

docs/api/graph/graph.md

@@ -1,16 +1,16 @@
 The Graph API is the primary means to retrieve data from an Atlas store.
 
-The default response is a PNG image plotting data matching the 
-[Atlas Stack Language](../../asl/tutorial.md) expression along with optional parameters 
-to control time ranges, size, style, labels, etc. For a quick overview by example see 
+The default response is a PNG image plotting data matching the
+[Atlas Stack Language](../../asl/tutorial.md) expression along with optional parameters
+to control time ranges, size, style, labels, etc. For a quick overview by example see
 the [examples](examples.md) page.
 
-If graphs look familiar, that's because the design and language were inspired by 
+If graphs look familiar, that's because the design and language were inspired by
 [RRDtool](https://oss.oetiker.ch/rrdtool/). RRD style graphs offer concise and highly
 customizable views of time series data. While a number of observability tools offer
 dynamic charts, a major benefit of these PNG graphs is the ability to snapshot data
-in time, particularly when that data may expire from a high throughput data store; 
-PNGs are forever. Additionally, the majority of email and on-call systems support 
+in time, particularly when that data may expire from a high throughput data store;
+PNGs are forever. Additionally, the majority of email and on-call systems support
 images out of the box without having to worry about porting a dynamic graphing
 library to various browsers and clients.
 
@@ -31,10 +31,10 @@ Additional Output formats, including JSON, can be found in [Outputs](outputs.md)
 
 ### Data
 
-The only required query param is `q` which is the [query expression](../../asl/tutorial.md) 
-used by the user to select and manipulate data. The simplest API query you can make is 
+The only required query param is `q` which is the [query expression](../../asl/tutorial.md)
+used by the user to select and manipulate data. The simplest API query you can make is
 `/api/v1/graph?q=42`. This will produce a graph from Atlas with a straight line having a
-value of `42` for 3 hours[*](#defaults) with a legend including statistics for the query period. 
+value of `42` for 3 hours[*](#defaults) with a legend including statistics for the query period.
 
 All query params related to fetching data:
 
@@ -43,7 +43,7 @@ All query params related to fetching data:
 | `q`    | Query expression      | must be specified by user  | [expr](../../asl/tutorial.md)               |
 | `step` | Step size for data    | auto                       | [duration](../time-parameters.md#durations) |
 
-!!! Warning 
+!!! Warning
     In most cases users should not set `step` directly. The `step` parameter
     is deprecated.
 

docs/api/graph/heatmap.md

@@ -1,13 +1,13 @@
 Atlas primarily supports visualizing data in line charts. As of 1.8, Atlas can also visualize
 via heatmaps using the [`:heatmap`](../../api/graph/line-styles.md#heatmap) line style.
-The graph area is broken up into a series of cells and a count for each cell is incremented when 
-a measurement falls within the cells boundaries. Colors or shades of colors then fill in cells 
+The graph area is broken up into a series of cells and a count for each cell is incremented when
+a measurement falls within the cells boundaries. Colors or shades of colors then fill in cells
 based on the final count.
 
 ## Percentiles
 
 Heatmaps are particularly useful on top of [percentile](../../spectator/patterns/percentile-timer.md)
-metrics to analyze the entire measurement range. 
+metrics to analyze the entire measurement range.
 
 **Note** Using the [log linear](axis-scale.md#log-linear) scale will help to highlight clustered regions of measurements
 via `&scale=log-linear`. The example also uses data not available in the demo Atlas instance.
@@ -20,7 +20,7 @@ via `&scale=log-linear`. The example also uses data not available in the demo At
 
 ## Bounds
 
-The `&heatmap_l=` and `&heatmap_u` parameters can be used to narrow the range of cells 
+The `&heatmap_l=` and `&heatmap_u` parameters can be used to narrow the range of cells
 displayed in a heatmap. Heatmap bounds act on the _count_ of measurements in a cell and the
 palette colors or shades chosen. Depending on the bound limits, some cells may appear empty.
 
@@ -32,7 +32,7 @@ With Bounds (`&heatmap_l=1.2&heatmap_u=1.3`): /api/v1/graph?e=2012-01-01T00:00&q
 ## Palette
 
 The palette used for filling heatmap cells can be changed via the `&heatmap_palette=` parameter.
-By default, a color is chosen from the global palette (based on whether the heatmap is the 
+By default, a color is chosen from the global palette (based on whether the heatmap is the
 first or a later expression). A gradient is then applied to that color with a lighter gradient
 representing smaller cell counts and darker representing larger counts.
 
@@ -58,7 +58,7 @@ For further information, see [Custom Color Palettes](color-palettes.md#custom).
 
 ### Order of Expressions
 
-When overlaying expressions with a heatmap and using the default palette, the order of 
+When overlaying expressions with a heatmap and using the default palette, the order of
 expressions determines the color gradient used for cells. For example, if the heatmap
 expression is second in the query, the second palette color will be used as the gradient:
 

docs/api/graph/line-styles.md

@@ -92,7 +92,7 @@ percentage chart for a group by:
 Since 1.8.
 
 Plotting many time series with a heat map can be useful for identifying concentrations of
-measurements where individual lines may produce too much noise. 
+measurements where individual lines may produce too much noise.
 
 See [Heatmap](heatmap.md) for more details.
 

docs/api/graph/multi-y.md

@@ -31,7 +31,7 @@ By default all axes will pick up [axis settings](../../asl/ref/axis.md) with no
 @@@
 
 Bounds and other axis settings can be set per axis, e.g., this graph moves the constant line for
-`42` to a separate axis and sets the lower bound to `0` via the `&l.1=0` parameter. This would 
+`42` to a separate axis and sets the lower bound to `0` via the `&l.1=0` parameter. This would
 work as well for `&u.1=100e3`. Append the index after the `l.` or `u.` :
 
 @@@ atlas-uri

docs/api/graph/tick.md

@@ -75,7 +75,7 @@ way of doing that is to disable the Y-axis labels by setting the tick label mode
 In situations where a graph has very small changes in value that generate a significant number
 of digits per tick, ticks may be labeled with offsets in order to fit the labels in
 the layout. A base value is displayed at the bottom of the axis and positive
-or negative offsets from the base displayed next to the ticks. 
+or negative offsets from the base displayed next to the ticks.
 
 For example, if the amount of disk space used varies by 1 byte occasionally, the ticks
 will be labeled by in increments of `+1.0`.
@@ -88,6 +88,6 @@ will be labeled by in increments of `+1.0`.
     It is possible for queries spanning different data sources to display offset labels due
     to differing schemes used to encode floating point values.
 
-If offsets are not desirable, try adjusting the y [axis bounds]. 
+If offsets are not desirable, try adjusting the y [axis bounds].
 
 [axis bounds]: axis-bounds.md

docs/api/tags.md

@@ -23,9 +23,9 @@ Specifies the output format to use. The default is `json`.
 
 ### Limit (limit)
 
-Maximum number of results to return before paging the response. If the response is paged 
-a `x-nflx-atlas-next-offset` will be set to indicate the next offset. Pass the value with an 
-[offset](#offset-offset) param to get the next part of the list. If the header is not present 
+Maximum number of results to return before paging the response. If the response is paged
+a `x-nflx-atlas-next-offset` will be set to indicate the next offset. Pass the value with an
+[offset](#offset-offset) param to get the next part of the list. If the header is not present
 there is no more data.
 
 ### Offset (offset)
@@ -36,5 +36,5 @@ If the response is paged this param is used to indicate where the next request s
 
 Query expression used to select a set of metrics and manipulate them for
 presentation in a graph. The query expression can use query
-and std commands described in the reference. 
+and std commands described in the reference.