anchor.diff:  
   == Consuming messages
   
  -The Yammer component provides several endpoints for consuming
  -messages:
  +The Yammer component provides several endpoints for consuming messages:
   
   [width="100%",cols="2l,3",options="header",]
   |=======================================================================
  
positive.code: |View data about the current user.
  |=====================================================
  
  
  == Using an enricher
  
  It is helpful sometimes (or maybe always in the case of users
  to use an enricher pattern rather than a route
  initiated with one of the polling consumers in camel-yammer. This is
  because the consumers will fire repeatedly, however often you set the
  delay for. If you just want to look up a user's data, or grab a message
  at a point in time, it is better to call that consumer once and then get
  one with your route.
  
  Lets say you have a route that at some point needs to go out and fetch
  user data for the current user. Rather than polling for this user over
  and over again, use the `pollEnrich` DSL method:
  
  [source,java]
  ----
  
negative.code: assertEquals("Hi from Camel!", messages.getMessages().get(0).getBody().getPlain());
  ----
  
  == Retrieving users
  
  The Yammer component provides several endpoints for retrieving users:
  
  [width="100%",cols="2l,3",options="header",]
  |=====================================================
  