anchor.diff:  
   === Using Query Annotations
   
  -The simples way to define a specific query is by annotating a method and
  +The simplest way to define a specific query is by annotating a method and
   providing the JPQL query string which has to be executed. In code, this
   looks like the following sample:
   
  
positive.code: :Notice: Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at. http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR  CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
  
  == Overview
  The Data module provides capabilities for implementing repository patterns and thereby simplifying the repository layer. Repository patterns are ideal for simple queries that require boilerplate code, enabling cenertalization of query logic and consequently reducing code duplication and improving testability.
  
  The code sample below gives you a quick overview on the common usage
  scenarios of the data module:
  
negative.code: 
  The implementation of the method is done automatically by the CDI
  extension. A client can declare a dependency to the interface only. The
  details on how to use those features are outlined in the following
  chapters.
  
  == Project Setup
  