merge

en/1-Beginner/Personal-Skills/04-How to Debug Using a Log.md

@@ -1,6 +1,6 @@
 # How to Debug Using a Log
 
-*Logging* is the practice of writing a system so that it produces a sequence of informative records, called a log. *Printlining* is just producing a simple, usually temporary, log. Absolute beginners must understand and use logs because their knowledge of the programming is limited; system architects must understand and use logs because of the complexity of the system. The amount of information that is provided by the log should be configurable, ideally while the program is running. In general, logs offer three basic advantages:
+*Logging* is the practice of writing a system so that it produces a sequence of informative records, called a log. *Printlining* is just producing a simple, usually temporary, log. Absolute beginners must understand and use logs because their knowledge of programming is limited; system architects must understand and use logs because of the complexity of the system. The amount of information that is provided by the log should be configurable, ideally while the program is running. In general, logs offer three basic advantages:
 
 - Logs can provide useful information about bugs that are hard to reproduce (such as those that occur in the production environment but that cannot be reproduced in the test environment).
 - Logs can provide statistics and data relevant to performance, such as the time passing between statements.
@@ -10,4 +10,4 @@ The amount to output into the log is always a compromise between information and
 
 If you have a permanent log, printlining can now be done in terms of the log records, and some of the debugging statements will probably be permanently added to the logging system.
 
-Next [How to Understand Performance Problems](05-How to Understand Performance Problems.md)
+Next [How to Understand Performance Problems](05-How to Understand Performance Problems.md)