anchor.diff:  }
   ----
   
  -Some use cases use <<scoreType,other `Score` types>>.
  +Some use cases use <<scoreType,other score types>>.
  +
  +This annotation can also be <<autoDiscoverSolutionProperties, auto discovered>> if enabled.
   
   
   [[getProblemFacts]]
  
positive.code: 
  [NOTE]
  ====
  A @PlanningEntityCollectionProperty annotation needs to be on a member in a class with a @PlanningSolution annotation.
  It is ignored on parent classes or subclasses without that annotation.
  ====
  
  In rare cases, a planning entity might be a singleton: use `@PlanningEntityProperty` on its getter (or field) instead.
  
  
  [[scoreOfASolution]]
  ==== `Score` of a Solution (``@PlanningScore``)
  
  A `Solution` requires a score property, which is annotated with a `@PlanningScore` annotation.
  The score property is `null` if the the score hasn't been calculated yet.
  The `score` property is typed to the specific `Score` implementation of your use case.
  For example, `NQueens` uses a <<simpleScore,SimpleScore>>:
  
negative.code: 
  
  [[planningEntitiesOfASolution]]
  ==== Planning Entities of a Solution (``@PlanningEntityCollectionProperty``)
  
  Planner needs to extract the entity instances from the solution instance.
  It gets those collection(s) by calling every getter (or field) that is annotated with ``@PlanningEntityCollectionProperty``:
  