From d5e54c773f65da5111021046f22514ff3dd7a013 Mon Sep 17 00:00:00 2001 From: Paul Fitzgerald Date: Mon, 5 Sep 2016 00:07:31 +0100 Subject: [PATCH] Update routes-defining.md --- routes-defining.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/routes-defining.md b/routes-defining.md index 44e4580..fe06474 100644 --- a/routes-defining.md +++ b/routes-defining.md @@ -68,7 +68,7 @@ After this there are two properties which can use to modify how routes are handl `useURL` tells `bigwheel` that the Browsers location should be changed when the section is brought in. By default `bigwheel` will change the url when navigating to sections (`useURL == true`). -If you set `useURL` to `false` then the url will never bed updated and also the section cannot be accessed by manually updating the browser's location. +If you set `useURL` to `false` then the url will never be updated and also the section cannot be accessed by manually updating the browser's location. In the above routes example if a user went in and typed: ```javascript @@ -125,4 +125,4 @@ module.exports = { As you can see to define multi section routes you just define your sections in an array using the standard form or using a section descriptor. What will happen is that when the route resolves all the sections will be run in tandem so all `init`, `resize`, `animateIn`, `animateOut`, and `destroy` calls will happen at the same time for all multi sections. -The reason why this is handy is that if you define `Menu` as an `Object` instead of a `function` `Menu` will always be persistent and it can react to sections coming in for instance highlighting the correct menu button in the `animateIn` function. \ No newline at end of file +The reason why this is handy is that if you define `Menu` as an `Object` instead of a `function` `Menu` will always be persistent and it can react to sections coming in for instance highlighting the correct menu button in the `animateIn` function.