Adding quick-fixes for typo/wording improvements for the Getting Started...

The full feedback from @mikes-caplin
---

- [ ] 1.       The Tomcat download was 8.4Mb, the BladeRunnerJS one was 110Mb.
- [x] 2.       Around the ‘Download & Install BRJS’ heading I saw several comments about where to ‘execute the brjs command’.  So I did.  I got

>C:\progs\BladeRunner\sdk>brjs
>Placeholder jsdoc generated for app 'dashboard'.
>Placeholder jsdoc generated for app 'dashboard-services'.
>BladeRunner version: v0.1-0-gc411f78, built: 29 October 2013 14:19 GMT
> 
>No such command ''
> 
>C:\progs\BladeRunner\sdk> 

I’d like a nicer first interaction.  I.e. a usage message at least if I don’t pass in a parameter to the brjs command.

- [x] 3.       I was mildly surprised that I couldn’t view the default aspect just by typing ‘brjs start’.  Maybe warn me earlier that I’ll need to start a browser too?
- [x] 4.       Make the http://localhost:7070/brjs-todo a link?  It worked fine clicking it from this mail (once I had brjs running).
- [x] 5.       Create a Bladeset.  I’d like to know the shape of the command, as well as exactly what to type.  Also I needed a second command window, as my other one is now running the BRJS server.
- [x] 6.       Scaffold the blade.  Again it would be nice to know the shape of the command I’m using.  E.g. brjs create-blade <app-name> <bladeset-name> <new-blade-name>
- [x] 7.       View the Code – the first path is wrong.  It should start apps/brjs-todo/todo-bladeset/…  and it should end /src/brjstodo/todo/todoinput.  So the whole is  apps/brjs-todo/todo-bladeset/blades/todoinput/src/bjrstodo/todo/todoinput/src/brjstodo/todo/todoinput
As that is where the ExamplePresentationModel.js file is found.
- [x] 8.       Run the blade in a workbench – can the workbench link(http://localhost:7070/brjs-todo/todo-bladeset/blades/todoinput/workbench/) be made a link?
- [x] 9.       I don’t get the Messages option top left in your screenshot.
- [x] 11.   Add Two-Way Data Binding  - typo:  Next, let’s edit the Blade to display an <input> element…
- [x] 12.   In the “We also update view.html to contain an input element…” paragraph between the two screenshots we say ‘we also want to call the newly named enterPressed function…’, but the function is actually called: keyPressed.
- [x] 13.   At the end of that sentence we should probably say more than Enter/Return.  Probably ‘… to see if it’s the Enter/Return key that is pressed.’?
- [x] 14.   Run the test – typo: first sentence ‘ you will find configuration…’, not fine
- [x] 15.   Run the test – can this be made a link? http://localhost:4224/capture?strict
- [x] 16.   Can we make it a link?  http://localhost:7070/brjs-todo/todo-bladeset/blades/todoitems/workbench/
- [x] 17.   And this http://localhost:7070/brjs-todo/todo-bladeset/blades/todoinput/workbench/
- [ ] 18.   Testing via a Unit Test – why do we need a ; before the (function() {  ??
- [x] 19.   Where does ‘added’ come from in ExamplePresentationModel.prototype._todoAdded = function( added )?
- [x] 20.   Testing in the Workbench.  Make this a link: http://localhost:7070/brjs-todo/todo-bladeset/blades/todoitems/workbench/
- [x] 21.   Also I got an error at this point.  I.e. Uncaught ReferenceError: ServiceRegistry is not defined
- [x] 22.   Because I had missed adding this line to my class: var ServiceRegistry = require(‘br/ServiceRegistry’);
- [x] 23.   Can we bold the lines to be added to existing files.  And also name those files and their directories.  I was interrupted (by several days) in completing the guide, and had to work out which file I should be adding to.
- [ ] 24.   Testing via a Unit test:  I replaced the contents of the ExampleClassTest.js file and the test failed.  The error message wasn’t too helpful:
![image002](https://f.cloud.github.com/assets/328367/1493873/0c3d2384-47d3-11e3-8c6d-406825c8e2fc.png)
- [ ] 26.   The reason being I hadn’t put the test into the .js file yet.
- [ ] 27.   It would be worth a) Highlighting that this is the todoitems test and not the todoinput test; and b) given we don’t have great feedback on tests yet, then an example using the screenshot above to say if you get this, do check that you have copied the test into your test file.
- [x] 28.   Adding the Blades to an Aspect.  Typo:  Instead of ‘updated it to look as follows:’ should be ‘update it to look as follows:’
- [ ] 29.   The section tag is not supported in IE8.  Are we okay with that?
- [x] 30.   Easier if the code to paste in is highlighted.
- [ ] 31.   The Guide says “The element with the ID of header will have the Todo Input element appended to it and the section with the ID of main will have the Todo List appended to it.”  I’d like to know why?
- [ ] 32.   It is explained in this paragraph: In order for the Blade components to appear in the aspect we have to append the DOM elements that the PresenterComponentinstances create to the Aspect - the main view into the Todo List web app. We do this by creating a SimpleFrame object and passing in the component to the constructor, then we can access the generated element via a getElement function on the frame object and simply appending it to the appropriate element in the DOM; for the Input we append to an element with an ID of header and for the List we append to an element with the ID of main: but it would be nice to say we’ll be explaining it below (even if just ‘see below’).
- [ ] 33.   I found the above paragraph confusing, and had to read it 2 or 3 times.  Is there a diagram that could go with it?
- [ ] 34.   Styling I got this error:  GET http://localhost:7070/brjs-todo/v_20131107115541/css/standard_css.bundle 500 (Error while bundling file. Caused by: URI "&#39;bg.png&#39;" is invalid (Illegal character in fragment). Exception thrown whilst attempting to process file: 'C:\progs\BladeRunner\apps\brjs-todo\default-aspect\themes\standard\style.css'.) localhost/:11, and the page did not change.
- [ ] 35.   I’d download the github links to the files, rather than the files themselves.  I went back and got the files themselves (no download link though), and replaced them, and all was well.
- [ ] 36.   Build and deploy.  You need to take the ./ out of the command for it to work on Windows.
- [ ] 37.   The .war file is 27Mb.
- [x] 38.   Deployed onto resin-4.0.35, and all worked first time.  And I could add more items to the list.

---
... Guide for @leggeter to review

7 (View the code js file path reference correction)
9/10 - Updating all getting-started screenshots which had the 'Messages' widget on workbench pages on the left as these have been removed from the template
11 Fixing typo for first para of Add Two-Way Data Binding
12 Fixing function reference 'enterPressed' -> 'keyPressed'
13 Changing 'to see if it's the *Enter/Return*' -> 'to see if it was the *Enter/Return* key'
14 This was resolved when the 'Run the Test' section was reworked after adding --no-browser flag support
28 Typo fix: 'updated it to look as follows' -> 'update it to look as follows'