delete region definition from layout regions hash when removing region
delete region definition from layout regions hash when removing region; take 2
Ignore some files and directories for Bower installs

When installing backbone.marionette through Bower, there are a lot of additional files added. This can be ignored.

I used something similar to this: https://github.com/twitter/flight/commit/e5fc35d9d8d6ae0431be4fd6052ce151bb2c0c66
addition of core directory has broken volo add command url path. This fixes the path.
Correcting property to be passed for updated Backbone fetch() method.

See http://backbonejs.org/#upgrading
If you want to smartly update the contents of a Collection, adding new models, removing missing ones, and merging those already present, you now call set (previously named "update"), a similar operation to calling set on a Model. This is now the default when you call fetch on a collection. To get the old behavior, pass {reset: true}
Fix typos in changelog
Added appRoute method for adding singular routes easier
Added alternative app.getRegion(regionName) method for better api and support for tooling.
Update marionette.application.js

Fix tabs x spaces.
Allow AppRouter to be instantiated through the constructor instead of .extend().
Currently, options.appRoutes is not used if "new AppRouter({...})" is used.
Update marionette.layout.md

mention some key benefits in intro, fix passive voice - hopefully thats clearer?
Update marionette.region.md

hopefully clarify, and mention regions within layouts
Update upgradeGuide.md

the correct option for `collection.fetch()` is `{reset: true}`
Marionette.triggerMethod checks for trigger before calling
Update marionette.view.md

Backbone.Events.listenTo no longer accepts a 4th 'context' parameter. Updated documentation to reflect this, including an example of the workaround for those cases where it is desired.
place existing comments with the right function

Reading the annotated source is confusing otherwise. handleShow()
is for when the view is shown and handleRender is for when it's
rendered, not the other way around.
Fix each example that erroneously used <%=, rather than <%
Update marionette.layout.js

Layout.render assumes that if the view is closed, it has been previously rendered. This assumption is valid in a 100% Marionette application; however, when mid-migration to Marionette pre-existing view handling may not respect this invariant.

Without this change the regions are uninitalized in `onRender` despite the layout having been rendered.

I haven't prepared tests for this change yet, but this change resolved the associated bug in the application I am migrating to Marionette. I will add them when I get a chance.
Merge pull request #641 from radar/patch-1

Fix each example that erroneously used <%=, rather than <%
Merge pull request #634 from depoulo/patch-1

Update upgradeGuide.md