docs: fixed name inconsistencies

Author: pmbittner

README.md

@@ -72,7 +72,7 @@ Moreover, the results comprise the (LaTeX) tables that are part of our paper and
 DiffDetective is documented with javadoc. The documentation can be accessed on this [website][documentation]. Notable classes of our library are:
 - [DiffTree](https://variantsync.github.io/DiffDetective/docs/javadoc/org/variantsync/diffdetective/diff/difftree/DiffTree.html) and [DiffNode](https://variantsync.github.io/DiffDetective/docs/javadoc/org/variantsync/diffdetective/diff/difftree/DiffNode.html) implement variation diffs from our paper. A variation diff is represented by an instance of the `DiffTree` class. It stores the root node of the diff and offers various methods to parse, traverse, and analyze variation diffs. `DiffNode`s represent individual nodes within a variation diff.
 - [Validation](https://variantsync.github.io/DiffDetective/docs/javadoc/org/variantsync/diffdetective/validation/Validation.html) contains the main method for our validation.
-- [ProposedElementaryPatterns](https://variantsync.github.io/DiffDetective/docs/javadoc/org/variantsync/diffdetective/pattern/elementary/proposed/ProposedElementaryPatterns.html) holds the catalog of the nine edit classes we proposed in our paper. It implements the interface [ElementaryPatternCatalogue](https://variantsync.github.io/DiffDetective/docs/javadoc/org/variantsync/diffdetective/pattern/elementary/ElementaryPatternCatalogue.html), which allows to define custom edit classifications.
+- [ProposedEditClasses](https://variantsync.github.io/DiffDetective/docs/javadoc/org/variantsync/diffdetective/editclass/proposed/ProposedEditClasses.html) holds the catalog of the nine edit classes we proposed in our paper. It implements the interface [EditClassCatalogue](https://variantsync.github.io/DiffDetective/docs/javadoc/org/variantsync/diffdetective/editclass/EditClassCatalogue.html), which allows to define custom edit classifications.
 - [BooleanAbstraction](https://variantsync.github.io/DiffDetective/docs/javadoc/org/variantsync/diffdetective/feature/BooleanAbstraction.html) contains data and methods for boolean abstraction of higher-order logic formulas. We use this for macro parsing.
 - [GitDiffer](https://variantsync.github.io/DiffDetective/docs/javadoc/org/variantsync/diffdetective/diff/GitDiffer.html) may parse the history of a git repository to variation diffs.
 - The [datasets](https://variantsync.github.io/DiffDetective/docs/javadoc/org/variantsync/diffdetective/datasets/package-summary.html) package contains various classes for describing and loading datasets.
@@ -95,7 +95,7 @@ How to build our library and how to run the example is described in the [proofs/
 ## 4. Dataset Overview
 ### 4.1 Open-Source Repositories
 We provide an overview of the used 44 open-source preprocessor-based software product lines in the [docs/datasets.md][dataset] file.
-As described in our paper in Section 5.1 this list contains all systems that were studied by Liebig et al., extended by four new subject systems (Busybox, Marlin, LibSSH, Godot).
+As described in our paper in Section 5.1, this list contains all systems that were studied by Liebig et al., extended by four new subject systems (Busybox, Marlin, LibSSH, Godot).
 We provide updated links for each system's repository.
 
 ### 4.2 Forked Repositories for Replication

STATUS.md

@@ -3,7 +3,7 @@
 The artifact for the paper _Classifying Edits to Variability in Source Code_ consists of four parts:
 
 1. **DiffDetective**: For our validation, we built DiffDetective, a java library and command-line tool to classify edits to variability in git histories of preprocessor-based software product lines. 
-  DiffDetective is the main artifact used to replicate the validation for our paper (see Section 5).
+  DiffDetective is the main artifact used to replicate the validation of our paper (see Section 5).
   DiffDetective is self-contained in that it does not require or depend on in-depth knowledge on the theoretical foundation of our work.
   Practitioners and researches are free to ignore the appendix as well as the haskell formalization and may use DiffDetective out-of-the-box.
 2. **Appendix**: The appendix of our paper is given in PDF format in the file [`appendix.pdf`][ddappendix].
@@ -22,14 +22,14 @@ DiffDetective is designed as a library that offers reusable functionality.
 Researchers and practitioners can use our DiffDetective library to build on our theory and results (e.g., for future prototypes to study the evolution of variability in source code).
 
 DiffDetective offers various features, including but not limited to:
-parsing variation tree diffs from unix diffs, obtaining variation tree diffs for certain patches and commits, matching elementary edit patterns on variation tree diffs, defining custom classifications, rendering, traversing, and transforming variation tree diffs, various de-/serialization methods, and running analyses for the git histories of C preprocessor-based software product lines. We documented each part of the library and provide a [javadoc website][dddocumentation] within the repository.
+parsing variation diffs from unix diffs, obtaining variation diffs for certain patches and commits, classifying edits in variation diffs, defining custom classifications, rendering, traversing, and transforming variation diffs, various de-/serialization methods, and running analyses for the git histories of C preprocessor-based software product lines. We documented each part of the library and provide a [javadoc website][dddocumentation] within the repository.
 Moreover, our validation (see _replicability_ above) may also be run on any custom dataset as described in our [README.md][ddreadme].
 
 ### **Extended Formal Specification**
 The [`proofs`][ddproofs] Haskell project provides an extended formal specification of our theory.
 Its main purpose is to document the theory and its extensions to serve as a reference for the proofs in our appendix.
 Yet, the project can also be used as a library to reason on variation trees and diffs in Haskell projects.
-The library is accompanied by a small demo application that shows an example test case for our proof of completeness by creating a variation tree diff from two variation trees and re-projecting them.
+The library is accompanied by a small demo application that shows an example test case for our proof of completeness by creating a variation diff from two variation trees and re-projecting them.
 The `proofs` project is described in detail in our appendix.
 
 ## Claims