style: revise for better English

.cz-config.js

 module.exports = {
   types: [
-    { value: 'tr-s', name: 'tr-s:     Small addition to or revision of Technical reference.' },
-    { value: 'tr-m', name: 'tr-m:     Medium addition to or revision of Technical reference.' },
-    { value: 'tr-l', name: 'tr-l:     Huge contribution to or revision of Technical reference.' },
+    { value: 'tr-s', name: 'tr-s:     Small addition to or revision of the Technical Reference.' },
+    { value: 'tr-m', name: 'tr-m:     Medium addition to or revision of the Technical Reference.' },
+    { value: 'tr-l', name: 'tr-l:     Huge contribution to or revision of the Technical Reference.' },
     { value: 'feat', name: 'feat:     A new feature' },
     { value: 'fix', name: 'fix:      A bug fix' },
-    { value: 'docs', name: 'docs:     General documentation only changes' },
+    { value: 'docs', name: 'docs:     General documentation-only changes' },
     {
       value: 'style',
       name:
-        'style:    Changes that do not affect the meaning of the code\n            (white-space, formatting, missing semi-colons, etc)',
+        'style:    Changes that do not affect the meaning of the code\n            (white-space, formatting, missing semicolons, etc)',
     },
     { value: 'test', name: 'test:     Adding missing tests' },
     {
@@ -25,7 +25,7 @@ module.exports = {
     {
       value: 'chore',
       name:
-        'chore:    Other changes that modify other than source or test files'
+        'chore:    Other changes that modify files other than source or test files'
     },
     { value: 'revert', name: 'revert:   Revert to a commit' },
   ],
@@ -48,7 +48,7 @@ module.exports = {
     scope: '\nDenote the SCOPE of this change (optional):',
     // used if allowCustomScopes is true
     customScope: 'Denote the SCOPE of this change:',
-    subject: 'Write a SHORT, IMPERATIVE tense description of the change:\n',
+    subject: 'Write a SHORT, IMPERATIVE mood description of the change:\n',
     body: 'Provide a LONGER description of the change (optional). Use "|" to break new line:\n',
     breaking: 'List any BREAKING CHANGES (optional):\n',
     footer: 'Reference ISSUES touched by this change (optional). E.g.: closes #31, see #34:\n',

README.md

@@ -29,7 +29,7 @@ To run commitizen on `git commit` rather than on `git cz`, update or create `.gi
 exec < /dev/tty && node_modules/.bin/git-cz --hook || true
 ```
 
-We have configured three types of commits for the work on the technical reference that should reflect the amount of your contribution:
+We have configured three types of commits for the work on the technical reference that should reflect the extent of your contribution:
 
 - tr-s:     Small addition to or revision of Technical reference.
 - tr-m:     Medium addition to or revision of Technical reference.

package.json

 {
   "name": "technical-reference",
   "version": "0.1.0",
-  "description": "A document describing how the software development process works in Göttingen State and University Library's Research and Development Department.",
+  "description": "A document describing the software development process at Göttingen State and University Library's Research and Development Department.",
   "repository": {
     "type": "git",
     "url": "https://gitlab.gwdg.de/fe/technical-reference.git"