anchor.diff:          <strong>limit</strong> - Limit the maximum number of items per page.
         </p>
         <p>
  -        <strong>rlid</strong> - Memberships having access of this resource link.
  +        <strong>rlid</strong> - Memberships having access to this resource link.
         </p>
         <p>
  -        The following code fetches first 5 users with role
  +        The following code fetches first five users with role
           <em>urn:lti:role:ims/lis/Learner</em> who have access to a resource
           link with ID rl999.
           <pre>
  
positive.code:     </p>
      <h3>Deep Linking</h3>
      <p>
        The deep linking provides a more intuitive way to add various types of
        content items from a Tool Provider (TP) into the tool consumer. This
        extension supports different types of content items such as a hyperlink,
        an embedded image or other media type, embedded HTML, iframe and a file.
        A typical use case as mentioned on IMS website would be: "to allow a user
        within a Tool Consumer (TC) to click a button on the toolbar of a text
        box editor, which opens a TP within an iframe (or pop-up window), use the
        interface provided to select one or more items, and have the selected
        item(s) returned to the TC and inserted into the text box.  This may be
        an instructor adding content to a content page, or could be a student
        selecting an attachment to submit as part of an assignment".
      </p>
      <p>
        The first step in deep linking message is that a POST request is
  
negative.code:       <em>ContentItemSelectionRequest</em>. The next step is for a Tool
        Provider is to verify if it is a valid LTI request and after that provide
        an interface for selecting content items. Once user select content items,
        Tool Provider should return the details of selected items in a JSON array
        back to the Tool Consumer at URL received in
        <em>content_item_return_url</em> parameter. Remember that, Tool Provider
        should always return user to the Tool Consumer even if they do not select
        any items.
      </p>
      <p>
        When a Tool Consumer sends a POST request to a Tool Provider, it may send
        the following parameters:
      </p>
      <strong>lti_message_type=</strong> ContentItemSelectionRequest (Required)
      <p>
  