Fix typo

garentee -> guarantee
Merge pull request #3625 from Evster88/master

Fix a simple documentation typo
[BUGFIX beta] Incorporate latest ember-dev fixes.

Prevents testing of multiple branches unless specifically enabled.
Also, enables features from `features.json` for tests.
Merge pull request #3628 from rjackson/update_ember-dev

[BUGFIX beta] Incorporate latest ember-dev fixes.
Revert "[FEATURE em-o] Added `Em.O` (shorthand for `Ember.Object.create`"

Core team consensus is that users who want this shorthand functionality
in their own app can easily create this alias.

This reverts commit e5848449c728d01f93176f0de2c9bed533129a78.
Better feature flagging for container-renderables
Update for 1.3.0 Canary
Remove experimental control helper
Don't use unreleased versions in the Gemfile.lock
Try something else to fix Travis build
Remove old require
Don't test 'dist=build' with enableallfeatures.
Merge pull request #3631 from rjackson/do_not_enable_all_features_in_built_tests

Don't test 'dist=build' with enableallfeatures.
[BUGFIX beta] reduceComputed supports non-array dependencies.

`ReduceComputedProperty`s want 3 kinds of dependencies.

1. non-array dependencies
2. array dependencies with normal (total invalidation) CP semantics
3. array dependencies with one-at-a-time semantics

It was previously only possible to create `reduceComputed`s with 3.  Macros
could be written that would manually handle 1. and 2.  For example,
`Ember.computed.sort` does this.

This commit makes possible all three cases.

```js
Ember.Object.extend({
  nonArray: 'string',
  totallyInvalidatingArray: [],
  oneAtATimeArray: [],

  computed: Ember.reduceComputed( 'nonArray',
                                  'totallyInvalidatingArray.[]',
                                  'oneAtATimeArray', {
    addedItem: function () { /* ... */ },
    removedItem: function () { /* ... */ }
  });
})
```

Arrays whose individual mutations should completely invalidate a
`reduceComputed` are specified by adding the `.[]` suffix to the dependent key.
Note that the items for this array are never passed to the `addedItem` and
`removedItem` callbacks: they should be treated much like non-array properties.

A straightforward motivating example is `Ember.computed.sort` - the items to be
sorted should be handled one-at-a-time, but the properties to sort by should
require a complete resort.

Fix #3600.