anchor.diff:  			
   			p Each update file should export a single function, which should accept a single argument - the <code>next(err)</code> callback, to be called when the update is complete.
   			
  -			p All the update files will be executed (each one waits for the previous update to complete) befor ethe web server is started.
  +			p All the update files will be executed (each one waits for the previous update to complete) before the web server is started.
   			
   			p If the <code>next</code> callback is receives an error it will be reported to the console, and application initialisation will halt.
   			
  
positive.code: 			a(name='concepts')
  			h1 Keystone Options
  			
  			p The options for KeystoneJS cover a range of beahviours, from how the express app is configured, to enabling features and authentication options for integrated services.
  			
  			p There are three ways to set options:
  			
  
negative.code: 					td
  						p Whether to enable built-in auth for Keystone's Admin UI, or a custom function to use to authenticate users.
  						p When this is set to <code class="default-value">false</code> (or not defined), Keystone's Admin UI will be open to the public (so set it!)
  						p If using a custom function, it should follow the standard for express middleware of <code>function(req, res, next)</code>. If a user is not logged in or should not access Keystone's Admin UI, use <code>res.redirect()</code> to redirect them - otherwise call the <code>next</code> callback to enable access.
  				tr
  					td <code>user model</code> <code class="data-type">String</code>
  					td
  