message: Updated codes.md - additional code-related cleanup
diff: # Element Codes
  -##CodeValue
  -Each BIS `Element` has a `CodeValue` string property that holds its *Code*--a human-readable identifier for the real-world entity that the Element represents.
  +##CodeValue Property
  +Each `Element` has a `CodeValue` string property that holds its *Code*--a human-readable identifier for the real-world entity that the Element represents.
  A Code conveys information to people and programs that understand the structure of the string and are therefore able to *decode* it.
  Different domains and organizations have different ways of *encoding* business information into the *Code*.
  @@ -28,13 +28,14 @@ When the identified entity is non-physical, it may have its *code* semi-permanen
  For example, a physical valve will have its serial number permanently affixed to it. The "Tag Number" of the "function" that the valve is performing in the process is stamped onto a "Tag" attached to the valve with a wire. If the valve is replaced with a new one (with a new serial number) the Tag holding function's "Tag Number" will be moved to the new valve.
  ## CodeSpec
  -Each `Element` has a `CodeSpec` navigation property relating it to a `CodeSpec` Element that governs its Code.
  A `CodeSpec` (aka **Code Specification**) captures the rules for encoding and decoding significant business information into and from a Code.
  -A Code Specification is used to generate and validate Codes using an independent 'Identification Code Service'.
  +A Code Specification can be used (e.g. by an 'Identification Code Service') to generate and validate Codes.
  +## CodeSpec Property
  +Each `Element` has a `CodeSpec` navigation property relating it to a `CodeSpec` that governs its Code.
  A single BIS Repository (e.g. an iModel) may use many Code Specifications--different classes of Elements can have different coding conventions.
  -## CodeScope
  +## CodeScope Property
  Each `Element` has a `CodeScope` navigation property that points to another Element that provides the uniqueness scope for its Code.
  The 'scoping' Element can represent the repository as a whole, a model, an assembly, etc.
  The 'scoping' Element could also represent some entity with a scope that is greater than the current BIS Repository. In this case, uniqueness within that scope can only be enforced by an external 'Identification Code Service'.
  @@ -43,7 +44,7 @@ For example, a Floor Code (like "1" or "2") must be unique within a Building, bu
  In this example, the Building instance is providing the CodeScope for the Floor.
  ## Uniqueness with a BIS Repsoitory
  -For a given Element, the combination of `CodeSpec`, `CodeScope`, and `CodeValue` must be unique within a BIS repository. In BIS Repositories, all `null` values are considered to be unique.
  +For a given Element, the combination of it `CodeSpec`, `CodeScope`, and `CodeValue` properties must be unique within the BIS repository. All `null` values are considered to be unique.
  > Next: [ElementAspect Fundamentals](./elementaspect-fundamentals.md)
  