the routing 'None' must be uppercased in the XML

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

diff --git a/doc/doxygen/platform.doc b/doc/doxygen/platform.doc
index e05bc6b..ad27aa9 100644 (file)
--- a/doc/doxygen/platform.doc
+++ b/doc/doxygen/platform.doc
@@ -141,7 +141,7 @@ Available attributes :
 Attribute name  | Mandatory | Values | Description
 --------------- | --------- | ------ | -----------
 id              | yes       | String | The identifier of an AS; facilitates referring to this AS. ID must be unique.
-routing         | yes       | Full\| Floyd\| Dijkstra\| DijkstraCache\| none\| Vivaldi\| Cluster | See Section \ref pf_rm for details.
+routing         | yes       | Full\| Floyd\| Dijkstra\| DijkstraCache\| None\| Vivaldi\| Cluster | See Section \ref pf_rm for details.
 
 
 <b>Example:</b>
@@ -1009,7 +1009,7 @@ basically 3 main kind of routing models :
 \subsubsection pf_raf The router affair
 
 Expressing routers becomes mandatory when using shortest-path based
-models or when using ns-3 or the bindings to the GTNetS packet-level
+models or when using the bindings to the ns-3 packet-level
 simulator instead of the native analytical network model implemented
 in SimGrid.
 
@@ -1017,7 +1017,7 @@ For graph-based shortest path algorithms, routers are mandatory,
 because both algorithms need a graph, and so we need to have source
 and destination for each edge.
 
-Routers are naturally an important concept in GTNetS or ns-3 since the
+Routers are naturally an important concept in ns-3 since the
 way they run the packet routing algorithms is actually simulated.
 Instead, the SimGrid’s analytical models aggregate the routing time
 with the transfer time. Rebuilding a graph representation only from
@@ -1056,7 +1056,7 @@ Floyd example :
                radical="0-1"   power="1000000000"    bw="125000000"     lat="5E-5"
         router_id="router1"/>
 
- <AS id="AS1" routing="none">
+ <AS id="AS1" routing="None">
     <host id="host1" power="1000000000"/>
  </AS>
 
@@ -1118,11 +1118,11 @@ Full example :
 
 \subsubsection pf_rm_sf Simple/fast models
 
-\li <b>none</b>: No routing (Unless you know what you are doing, avoid
+\li <b>None</b>: No routing (Unless you know what you are doing, avoid
 using this mode in combination with a non Constant network model).
 None Example :
 \verbatim
-<AS id="exitAS"  routing="none">
+<AS id="exitAS"  routing="None">
        <router id="exit_gateway"/>
 </AS>\endverbatim
 
@@ -1664,7 +1664,7 @@ characteristics (lookup : time to resolve a route):
     fast lookup, small memory requirements, shortest path routing
     only). Same as Dijkstra, except it handles a cache for latest used
     routes.
-\li <b>none</b>: No routing (usable with Constant network only).
+\li <b>None</b>: No routing (usable with Constant network only).
     Defines that there is no routes, so if you try to determine a
     route without constant network within this AS, SimGrid will raise
     an exception.
@@ -1676,8 +1676,8 @@ characteristics (lookup : time to resolve a route):
 
 Actually we did not include switch tag, ok. But when you're trying to
 simulate a switch, the only major impact it has when you're using
-fluid model (and SimGrid uses fluid model unless you activate GTNetS,
-ns-3, or constant network mode) is the impact of the upper limit of
+fluid model (and SimGrid uses fluid model unless you activate 
+ns-3 or constant network mode) is the impact of the upper limit of
 the switch motherboard speed that will eventually be reached if you're
 using intensively your switch. So, the switch impact is similar to a
 link one. That's why we are used to describe a switch using a link tag