From: Philipp Holzer <admin@philipp.info>
Date: Sun, 3 Mar 2019 20:38:33 +0000 (+0100)
Subject: typo
X-Git-Url: https://git.mxchange.org/?a=commitdiff_plain;h=cc8a6c85ae939c0fc9258d7a11276bc7c2e59bc0;p=friendica.git

typo
---

diff --git a/src/Util/Logger/README.md b/src/Util/Logger/README.md
new file mode 100644
index 0000000000..381bd94ba7
--- /dev/null
+++ b/src/Util/Logger/README.md
@@ -0,0 +1,29 @@
+## Friendica\Util\Logger
+
+This namespace contains the different implementations of a Logger.
+
+### Configuration guideline
+
+The following settings are possible for `logger_config`:
+-	`monolog`: A Logging framework with lots of additions (see [Monolog](https://github.com/Seldaek/monolog/)). There are just Friendica additions inside the Monolog directory
+-	[`stream`](StreamLogger.php): A small logger for files or streams
+-	[`syslog`](SyslogLogger.php): Prints the logging output into the syslog
+
+[`VoidLogger`](VoidLogger.php) is a fallback logger without any function if no debugging is enabled.
+
+[`ProfilerLogger`](ProfilerLogger.php) is a wrapper around an existing logger in case profiling is enabled for Friendica.
+Every log call will be saved to the `Profiler` with a timestamp.
+
+### Implementation guideline
+
+Each logging implementation should pe capable of printing at least the following information:
+-	An unique ID for each Request/Call
+-	The process ID (PID)
+-	A timestamp of the logging entry
+-	The critically of the log entry
+-	A log message
+-	A context of the log message (f.e which user)
+
+If possible, a Logger should extend [`AbstractFriendicaLogger`](AbstractFriendicaLogger.php), because it contains additional, Friendica specific business logic for each logging call.
+
+Using AbstractFriendicaLogger makes the logger capable of adding profiling data for each log call.
diff --git a/src/Util/Logger/REAMDE.md b/src/Util/Logger/REAMDE.md
deleted file mode 100644
index 381bd94ba7..0000000000
--- a/src/Util/Logger/REAMDE.md
+++ /dev/null
@@ -1,29 +0,0 @@
-## Friendica\Util\Logger
-
-This namespace contains the different implementations of a Logger.
-
-### Configuration guideline
-
-The following settings are possible for `logger_config`:
--	`monolog`: A Logging framework with lots of additions (see [Monolog](https://github.com/Seldaek/monolog/)). There are just Friendica additions inside the Monolog directory
--	[`stream`](StreamLogger.php): A small logger for files or streams
--	[`syslog`](SyslogLogger.php): Prints the logging output into the syslog
-
-[`VoidLogger`](VoidLogger.php) is a fallback logger without any function if no debugging is enabled.
-
-[`ProfilerLogger`](ProfilerLogger.php) is a wrapper around an existing logger in case profiling is enabled for Friendica.
-Every log call will be saved to the `Profiler` with a timestamp.
-
-### Implementation guideline
-
-Each logging implementation should pe capable of printing at least the following information:
--	An unique ID for each Request/Call
--	The process ID (PID)
--	A timestamp of the logging entry
--	The critically of the log entry
--	A log message
--	A context of the log message (f.e which user)
-
-If possible, a Logger should extend [`AbstractFriendicaLogger`](AbstractFriendicaLogger.php), because it contains additional, Friendica specific business logic for each logging call.
-
-Using AbstractFriendicaLogger makes the logger capable of adding profiling data for each log call.