X-Git-Url: http://bilbo.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/dccf1b41e9c7b5a696f01abceaa2779fe65f154f..fe351f7439d06e7b0a7621ba282ea27c536133f9:/doc/doxygen/outcomes_logs.doc
diff --git a/doc/doxygen/outcomes_logs.doc b/doc/doxygen/outcomes_logs.doc
index 669b0e672b..e22541c2f3 100644
--- 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.
@@ -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 add keyword allows to specify the additivity of a
+The add 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
+*/