X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/90e4c5ad80e72c1ddfe0ceaa527ed76b1d51e0a2..f6755a2f88d16e9249253ee380f3555f1cfdb085:/doc/doxygen/outcomes_vizu.doc

diff --git a/doc/doxygen/outcomes_vizu.doc b/doc/doxygen/outcomes_vizu.doc
index d8cecd86b5..d8a7ad3267 100644
--- a/doc/doxygen/outcomes_vizu.doc
+++ b/doc/doxygen/outcomes_vizu.doc
@@ -239,7 +239,7 @@ This option changes the way SimGrid register its platform on the trace
 file. Normally, the tracing considers all routes (no matter their
 size) on the platform file to re-create the resource topology. If this
 option is activated, only the routes with one link are used to
-register the topology within an AS.  Routes among AS continue to be
+register the topology within a netzone. Routes among netzones continue to be
 traced as usual.
 \verbatim
 --cfg=tracing/onelink-only:yes
@@ -504,7 +504,7 @@ the beggining and size of the time slice.
 
 \subsubsection tracing_viva_graph Hierarchical Graph View
 
-%As stated above (see section \ref tracing_tracing_analyzing), one
+As stated above (see section \ref tracing_tracing_analyzing), one
 possibility to analyze SimGrid traces is to use Viva's graph view with
 a graph configuration to customize the graph according to the
 traces. A valid graph configuration (we are using the non-XML <a