anchor.diff:          |         }
           |     ]);
           |  
  +        |     // Callback, completes the registration process
           |     next();
           | }
           |  
  +        | // Required for all plugins
  +        | // If this were a npm module, one could do this:
  +        | // exports.register.attributes = require('package.json')
           | exports.register.attributes = {
  -        |     name: 'tasks-route',
  +        |     name: 'tasks-route', // Must be unique
           |     version: '1.0.0'
           | };
   p
  -    | This file will be responsible for all routes related to the 
  +    | This file will be responsible for all routes to the 
       code /tasks
       |  endpoint.
   p
  
positive.code:         | 
          | var server = new Hapi.Server();
          | 
          | // Create a server which will listen in port 8000
          | server.connection({
          |     host: 'localhost',
          |     port: 8000
  
negative.code:     br
      | The API will respond to 
      code GET
      |  requests on the 
      code /hello
      |  endpoint. And it should respond with the string 
      code world
      | . Any requests not directed to this endpoint will result in a 
      code 404
      |  response.
      | So let's see it in action. In one terminal session start the server:
  pre
      code.bash
          | $ node index.js
  p
      | And in another terminal session make a request to our API:
  pre
      code.bash
          | $ curl -XGET http://localhost:8000/hello
  p
      | If you see a response of 
      code world
      |  you've created your first hapi API server, yay!
  h2 Meet hapi plugins
  p
      | Plugins can do an array of things; They're plugins after all. For now we'll be using plugins to modularize the route we just created.
      br
      | Let's create a 
      code routes
  