Remove trailing spaces from docs

docs/axes/README.md

@@ -26,18 +26,18 @@ There are a number of config callbacks that can be used to change parameters in
 | Name | Arguments | Description
 | ---- | --------- | -----------
 | `beforeUpdate` | `axis` | Callback called before the update process starts.
-| `beforeSetDimensions` | `axis` | Callback that runs before dimensions are set. 
+| `beforeSetDimensions` | `axis` | Callback that runs before dimensions are set.
 | `afterSetDimensions` | `axis` | Callback that runs after dimensions are set.
 | `beforeDataLimits` | `axis` | Callback that runs before data limits are determined.
 | `afterDataLimits` | `axis` | Callback that runs after data limits are determined.
 | `beforeBuildTicks` | `axis` | Callback that runs before ticks are created.
 | `afterBuildTicks` | `axis` | Callback that runs after ticks are created. Useful for filtering ticks.
 | `beforeTickToLabelConversion` | `axis` | Callback that runs before ticks are converted into strings.
-| `afterTickToLabelConversion` | `axis` | Callback that runs after ticks are converted into strings. 
+| `afterTickToLabelConversion` | `axis` | Callback that runs after ticks are converted into strings.
 | `beforeCalculateTickRotation` | `axis` | Callback that runs before tick rotation is determined.
 | `afterCalculateTickRotation` | `axis` | Callback that runs after tick rotation is determined.
-| `beforeFit` | `axis` | Callback that runs before the scale fits to the canvas. 
-| `afterFit` | `axis` | Callback that runs after the scale fits to the canvas. 
+| `beforeFit` | `axis` | Callback that runs before the scale fits to the canvas.
+| `afterFit` | `axis` | Callback that runs after the scale fits to the canvas.
 | `afterUpdate` | `axis` | Callback that runs at the end of the update process.
 
 ## Updating Axis Defaults

docs/axes/cartesian/time.md

@@ -147,6 +147,6 @@ The `ticks.source` property controls the ticks generation
 * `'labels'`: generates ticks from user given `data.labels` values ONLY
 
 ### Parser
-If this property is defined as a string, it is interpreted as a custom format to be used by moment to parse the date. 
+If this property is defined as a string, it is interpreted as a custom format to be used by moment to parse the date.
 
 If this is a function, it must return a moment.js object given the appropriate data value.

docs/charts/bar.md

@@ -6,12 +6,12 @@ A bar chart provides a way of showing data values represented as vertical bars.
     "type": "bar",
     "data": {
         "labels": [
-            "January", 
-            "February", 
-            "March", 
-            "April", 
-            "May", 
-            "June", 
+            "January",
+            "February",
+            "March",
+            "April",
+            "May",
+            "June",
             "July"
         ],
         "datasets": [{

docs/charts/mixed.md

@@ -41,9 +41,9 @@ At this point we have a chart rendering how we'd like. It's important to note th
   "type": "bar",
   "data": {
     "labels": [
-      "January", 
-      "February", 
-      "March", 
+      "January",
+      "February",
+      "March",
       "April"
     ],
     "datasets": [{

docs/charts/radar.md

@@ -8,9 +8,9 @@ They are often useful for comparing the points of two or more different data set
     "type": "radar",
     "data": {
         "labels": [
-            "Eating", 
-            "Drinking", 
-            "Sleeping", 
+            "Eating",
+            "Drinking",
+            "Sleeping",
             "Designing",
             "Coding",
             "Cycling",
@@ -94,7 +94,7 @@ The style of point. Options are:
 * 'circle'
 * 'cross'
 * 'crossRot'
-* 'dash'. 
+* 'dash'.
 * 'line'
 * 'rect'
 * 'rectRounded'
@@ -127,7 +127,7 @@ It is common to want to apply a configuration setting to all created radar chart
 
 ## Data Structure
 
-The `data` property of a dataset for a radar chart is specified as a an array of numbers. Each point in the data array corresponds to the label at the same index on the x axis. 
+The `data` property of a dataset for a radar chart is specified as a an array of numbers. Each point in the data array corresponds to the label at the same index on the x axis.
 
 ```javascript
 data: [20, 10]

docs/configuration/legend.md

@@ -10,7 +10,7 @@ The legend configuration is passed into the `options.legend` namespace. The glob
 | `display` | `Boolean` | `true` | is the legend shown
 | `position` | `String` | `'top'` | Position of the legend. [more...](#position)
 | `fullWidth` | `Boolean` | `true` | Marks that this box should take the full width of the canvas (pushing down other boxes). This is unlikely to need to be changed in day-to-day use.
-| `onClick` | `Function` | | A callback that is called when a click event is registered on a label item 
+| `onClick` | `Function` | | A callback that is called when a click event is registered on a label item
 | `onHover` | `Function` | | A callback that is called when a 'mousemove' event is registered on top of a label item
 | `reverse` | `Boolean` | `false` | Legend will show datasets in reverse order.
 | `labels` | `Object` | | See the [Legend Label Configuration](#legend-label-configuration) section below.

docs/configuration/tooltip.md

@@ -63,9 +63,9 @@ Example:
 Chart.Tooltip.positioners.custom = function(elements, eventPosition) {
     /** @type {Chart.Tooltip} */
     var tooltip = this;
-	    
+
     /* ... */
-	    
+
     return {
         x: 0,
         y: 0

docs/developers/charts.md

@@ -75,7 +75,7 @@ The built in controller types are:
 For example, to derive a new chart type that extends from a bubble chart, you would do the following.
 
 ```javascript
-// Sets the default config for 'derivedBubble' to be the same as the bubble defaults. 
+// Sets the default config for 'derivedBubble' to be the same as the bubble defaults.
 // We look for the defaults by doing Chart.defaults[chartType]
 // It looks like a bug exists when the defaults don't exist
 Chart.defaults.derivedBubble = Chart.defaults.bubble;
@@ -102,7 +102,7 @@ var custom = Chart.controllers.bubble.extend({
 
 // Stores the controller so that the chart initialization routine can look it up with
 // Chart.controllers[type]
-Chart.controllers.derivedBubble = custom; 
+Chart.controllers.derivedBubble = custom;
 
 // Now we can create and use our new chart type
 new Chart(ctx, {

docs/general/colors.md

@@ -6,7 +6,7 @@ You can also pass a [CanvasGradient](https://developer.mozilla.org/en-US/docs/We
 
 ## Patterns and Gradients
 
-An alternative option is to pass a [CanvasPattern](https://developer.mozilla.org/en-US/docs/Web/API/CanvasPattern) or [CanvasGradient](https://developer.mozilla.org/en/docs/Web/API/CanvasGradient) object instead of a string colour. 
+An alternative option is to pass a [CanvasPattern](https://developer.mozilla.org/en-US/docs/Web/API/CanvasPattern) or [CanvasGradient](https://developer.mozilla.org/en/docs/Web/API/CanvasGradient) object instead of a string colour.
 
 For example, if you wanted to fill a dataset with a pattern from an image you could do the following.
 

docs/general/interactions/README.md

@@ -1,6 +1,6 @@
 # Interactions
 
-The hover configuration is passed into the `options.hover` namespace. The global hover configuration is at `Chart.defaults.global.hover`. To configure which events trigger chart interactions, see [events](./events.md#events). 
+The hover configuration is passed into the `options.hover` namespace. The global hover configuration is at `Chart.defaults.global.hover`. To configure which events trigger chart interactions, see [events](./events.md#events).
 
 | Name | Type | Default | Description
 | ---- | ---- | ------- | -----------

docs/general/interactions/events.md

@@ -7,7 +7,7 @@ The following properties define how the chart interacts with events.
 | `onHover` | `Function` | `null` | Called when any of the events fire. Called in the context of the chart and passed the event and an array of active elements (bars, points, etc).
 | `onClick` | `Function` | `null` | Called if the event is of type 'mouseup' or 'click'. Called in the context of the chart and passed the event and an array of active elements
 
-## Event Option 
+## Event Option
 For example, to have the chart only respond to click events, you could do
 ```javascript
 var chart = new Chart(ctx, {

docs/general/interactions/modes.md

@@ -41,7 +41,7 @@ Finds the first item that intersects the point and returns it. Behaves like 'nea
 See `'index'` mode
 
 ## index
-Finds item at the same index. If the `intersect` setting is true, the first intersecting item is used to determine the index in the data. If `intersect` false the nearest item, in the x direction, is used to determine the index. 
+Finds item at the same index. If the `intersect` setting is true, the first intersecting item is used to determine the index in the data. If `intersect` false the nearest item, in the x direction, is used to determine the index.
 
 ```javascript
 var chart = new Chart(ctx, {