setting autocrlf = true on windows - no logical changes
diff --git a/slf4j-migrator/LIMITATIONS.txt b/slf4j-migrator/LIMITATIONS.txt
index dcba5dc..7770f24 100644
--- a/slf4j-migrator/LIMITATIONS.txt
+++ b/slf4j-migrator/LIMITATIONS.txt
@@ -1,35 +1,35 @@
-
-The slf4j-migrator aims to
-
-General limitations
-===================
-
-- the FATAL level is not supported.
-
- This is limitation is not deemed serious because there are usually
- very few log statements bearing the FATAL level.
-
-
-- if a method declares multipe loggers on the same line, the conversion will not be complete. Example:
-
-
- public void someMethod(Log l1, Log l2) {
- ...
- }
-
- will be converted as
-
- public void someMethod(Log l1, Logger l2) {
- ...
- }
-
-
-When migrating from log4j
-=========================
-
-- Since NDC is not supported by SLF4J, the migrator cannot properly handle
- NDC statements.
-
-- Calls to PropertyConfigurator or DomConfigurator cannot be migrated since
- SLF4J the equivalents.
+
+The slf4j-migrator aims to
+
+General limitations
+===================
+
+- the FATAL level is not supported.
+
+ This is limitation is not deemed serious because there are usually
+ very few log statements bearing the FATAL level.
+
+
+- if a method declares multipe loggers on the same line, the conversion will not be complete. Example:
+
+
+ public void someMethod(Log l1, Log l2) {
+ ...
+ }
+
+ will be converted as
+
+ public void someMethod(Log l1, Logger l2) {
+ ...
+ }
+
+
+When migrating from log4j
+=========================
+
+- Since NDC is not supported by SLF4J, the migrator cannot properly handle
+ NDC statements.
+
+- Calls to PropertyConfigurator or DomConfigurator cannot be migrated since
+ SLF4J the equivalents.
\ No newline at end of file