spellings mistakes in doc/

[simgrid.git] / doc / doxygen / outcomes_logs.doc

diff --git a/doc/doxygen/outcomes_logs.doc b/doc/doxygen/outcomes_logs.doc
index 669b0e6..bdebfd4 100644 (file)
--- a/doc/doxygen/outcomes_logs.doc
+++ b/doc/doxygen/outcomes_logs.doc
@@ -4,7 +4,7 @@
 
 Using @c printf or @c println to display information is possible, but
 quickly unpractical, as the logs of all processes get intermixed in
-your program's output. %As an answer, the SimGrid logging module allow
+your program's output. As an answer, the SimGrid logging module allow
 you to sort and filter the logs by emitter, by module and by gravity
 level. 
 
@@ -236,7 +236,7 @@ The most common setting is to control which logging event will get
 displayed by setting a threshold to each category through the
 <tt>threshold</tt> keyword.
 
-For example, @verbatim --log=root.threshold:debug@endverbatim will make
+For example, @verbatim --log=root.thresh:debug@endverbatim will make
 SimGrid <b>extremely</b> verbose while @verbatim
 --log=root.thres:critical@endverbatim should shut it almost
 completely off.
@@ -245,7 +245,7 @@ Note that the <tt>threshold</tt> keyword can be abbreviated here. For example,
 all the following notations have the same result.
 @verbatim
 --log=root.threshold:debug
---log=root.threshol:debug
+--log=root.threshold:debug
 --log=root.thresho:debug
 --log=root.thresh:debug
 --log=root.thres:debug
@@ -261,7 +261,7 @@ The full list of recognized thresholds is the following:
  - trace: enter and return of some functions
  - debug: crufty output
  - verbose: verbose output for the user wanting more
- - info: output about the regular functionning
+ - info: output about the regular functioning
  - warning: minor issue encountered
  - error: issue encountered
  - critical: major issue encountered 
@@ -306,12 +306,6 @@ Here are the existing format directives:
  - %%L: line number where the log event was raised (LOG4J compatible)
  - %%M: function name (LOG4J compatible -- called method name here of course).
 
- - %%b: full backtrace (Called %%throwable in LOG4J).
-   Defined only under windows or when using the GNU libc because backtrace() is not defined
-   elsewhere, and we only have a fallback for windows boxes, not mac ones for example.
- - %%B: short backtrace (only the first line of the %%b).
-   Called %%throwable{short} in LOG4J; defined where %%b is.
-
  - %%d: date (UNIX-like epoch)
  - %%r: application age (time elapsed since the beginning of the application)
 
@@ -363,7 +357,7 @@ manually.
 
 @subsubsection log_use_conf_add Category additivity
 
-The <tt>add</tt> keyword allows to specify the additivity of a
+The <tt>add</tt> keyword allows one to specify the additivity of a
 category (see @ref log_in_app). '0', '1', 'no', 'yes', 'on'
 and 'off' are all valid values, with 'yes' as default.
 
@@ -438,4 +432,4 @@ category's appender.
 
 The default appender function currently prints to stderr.
 
-*/
\ No newline at end of file
+*/