anchor.diff:  - lastName
   - category.name
   
  -Now we don't want category to be able to set description via the operation, how do we control/specify that? it makes
  -it hard to reason about which fields in an objects are not intended to be mutated. This is the reason we chose to
  +Now we don't want category to be able to set description via the operation, how do we control/specify that? It makes
  +it hard to reason about which fields in an object are not intended to be mutated. This is the reason we chose to
   limit it to objects that expose getters and setters.
   
  -NOTE: I know spring supports fields as well, and it will fall back to fields if setters are not found
  +NOTE: I know spring supports fields as well, and it will fall back to fields if setters are not found.
   
   [[q7]]*Q. How should we resolve multiple object mappers available as beans especially when using spring-hateoas?*
   
  
positive.code: 
  [[q11]]*Q. Why are all my operations not showing in the UI?*
  
  A.  This is a known limitation of swagger-spec. There is a work around for it but, swagger-ui won't play nice with it.
  I have a https://github.com/swagger-api/swagger-js/pull/541[PR] which address that issue. Would be great if you vote
  up the PR and the https://github.com/swagger-api/swagger-spec/issues/291[underlying issue]
  
  
negative.code: 
  [[q13]]*Q. How does one configure swagger-ui for non-springboot applications?*
  
  A. Excerpted from https://github.com/springfox/springfox/issues/983[issue 983]...
  
  I was able to get it working by modifying the `dispatcherServlet` to listen on /* , but this prevented `swagger-ui.html`
  from being served. To fix this to let the `swagger-ui.html` bypass the `dispatcherServlet` i had to create a new
  servlet mapping:
  
  [source,xml]
  