Correct capitalization in commit message instructions

emacscollective · Jul 11, 2023 · 1773bee · 1773bee
1 parent af53db5
commit 1773bee
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 4 deletions.
diff --git a/README.org b/README.org
@@ -189,7 +189,7 @@ be changed using a function, preferably in ~early-init.el~:
 *** (D) Commit messages
 
 1. Please theme each package using a separate commit and use commit
-   messages of the form ~PACKAGE: theme VARIABLE~.
+   messages of the form ~<package>: Theme <variable>~.
 
 2. If a package has several path variables, then you should theme them
    all in one commit.
@@ -198,7 +198,7 @@ be changed using a function, preferably in ~early-init.el~:
    use a message such as:
 
    #+begin_src text
-     foo: theme variables
+     foo: Theme variables
 
      Theme `foo-config-file', `foo-cache-directory',
      and `foo-persistent-file'.

diff --git a/no-littering.el b/no-littering.el
@@ -151,18 +151,19 @@
 ;;;;; D) Commit messages
 ;;
 ;; 1. Please theme each package using a separate commit and use commit
-;;    messages of the form "<package>: theme <variable".
+;;    messages of the form "<package>: Theme <variable".
 ;;
 ;; 2. If a package has several path variables, then you should theme them
 ;;    all in one commit.
 ;;
 ;; 3. If the variable names do not fit nicely on the summary line, then
 ;;    use a message such as:
 ;;
-;;      foo: theme variables
+;;      foo: Theme variables
 ;;
 ;;      Theme `foo-config-file', `foo-cache-directory',
 ;;      and `foo-persistent-file'.
+;;
 ;; 4. When appropriate add statements like the following to the commit
 ;;    message:
 ;;