From 0e195187836ae024c1508ec0d15e70b872e05ff3 Mon Sep 17 00:00:00 2001
From: mikaello <2505178+mikaello@users.noreply.github.com>
Date: Mon, 18 Mar 2024 11:28:33 +0100
Subject: [PATCH] docs: improve CR lint error message

Carriage Return (ASCII 13, CR) and Line Feed (ASCII 10, LF) are characters with standardized names that are used in various combinations to make a "New Line" or a "Newline". The correct, non-confusing wording of the error message would be "No files with CR (Carriage Return only Newline) found."
---
 Dockerfiles/data/file-cr | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Dockerfiles/data/file-cr b/Dockerfiles/data/file-cr
index 6b04a5f..b881a29 100755
--- a/Dockerfiles/data/file-cr
+++ b/Dockerfiles/data/file-cr
@@ -7,9 +7,9 @@ set -u
 
 # Name and messages
 MY_NAME="file-cr"
-MY_DESC="Scans recursively for files containing CR (Carriage Return only Line Feeds)."
-MY_FINISH_OK="No files with CR (Carriage Return only Line Feed) found."
-MY_FINISH_ERR="Files with CR (Carriage Return Line Feed) found."
+MY_DESC="Scans recursively for files containing CR (Carriage Return only newlines)."
+MY_FINISH_OK="No files with CR (Carriage Return only newline) found."
+MY_FINISH_ERR="Files with CR (Carriage Return newline) found."
 
 # Configuration file prefix
 MY_CONF_PRE="FILE_CR_"