Remove the failed glossary concept

Author: FreeApophis

documentation/C-Sharp Coding Guidelines.tex

@@ -46,9 +46,9 @@ \subsection{When and where are these rules applicable}
 In a review, these coding guidelines should be checked for all code, which has changed.
 Changes necessary due to the coding guidelines should be in a reasonable ratio to the functional changes.
 
-\subsection{Update to the rules and glossary}
+\subsection{Update to the rules}
 
-Updates to the rules and glossary should be sent to the developer council. The developer council will integrate new rules or new words in the glossary in a timely fashion when the board approves and will give feedback otherwise.
+Updates to the rules should be sent to the developer council. The developer council will integrate new rules in a timely fashion when the council approves and will give feedback otherwise.
 
 \subsection{Definition of done}
 
@@ -66,7 +66,7 @@ \section{Physical structure}
 
 \subsection{Each class should go into its own file with the same name}
 
-Only one class should be in a file. This also applies to Enumerations.
+Only one class should be in a file. This also applies to an Enumerations.
 Inner classes are allowed but discouraged and an obvious exception to this rule. 
 
 \subsection{Each namespace should go into its own folder with the same name}
@@ -119,7 +119,6 @@ \subsection{We use English words for abstractions}
   \item It is a lot easier to create plurals in English (-s, -ies) where in German it might be difficult: Kapitel, Mitarbeiter, Unternehmer, Fenster, Artikel (see also next point)
   \item Proper Nouns  should not be translated even if possible.
   \item We try to use the same word for the same abstraction. It is either a project or a tenant. (DDD)
-  \item All widely used concepts should be listed in the glossary
 \end{itemize}
 
 \subsection{Be specific}