-point) that allows to go out of the current network and reach other
-networks. At the upper level, these networks are known as
-<b>Autonomous System (AS)</b>, while at the lower level they are named
-sub-networks, or LAN. Indeed they are autonomous: routing is defined
-within the limits of his network by the administrator, and so, those
-networks can continue to operate without the existence of other
-networks. There are some rules to get out of networks by the entry
-points (or gateways). Those gateways allow you to go from a network to
-another one. Inside of each autonomous system, there is a bunch of
-equipments (cables, routers, switches, computers) that belong to the
-autonomous system owner.
-
-SimGrid platform description file relies exactly on the same concepts
-as real life platform. Every resource (computers, network equipments,
-and so on) belongs to an AS. Within this AS, you can define the
-routing you want between its elements (that's done with the routing
-model attribute and eventually with some \<route\> tag). You define AS
-by using ... well ... the \<AS\> tag. An AS can also contain some AS :
-AS allows you to define the hierarchy of your platform.
-
-Within each AS, you basically have the following type of resources:
-\li <b>host</b>: an host, with cores in it, and so on
+point); this allows to leave the current network and reach other
+networks, possibly even in other locations.
+At the upper level, such a network is called
+<b>Autonomous System (AS)</b>, while at the lower level it is named
+sub-network, or LAN (local area network).
+They are indeed autonomous: routing is defined
+(within the limits of his network) by the administrator, and so, those
+networks can operate without a connection to other
+networks. So-called gateways allow you to go from one network to
+another, if such a (physical) connection exists. Every node in one network
+that can be directly reached (i.e., without traversing other nodes) from
+another network is called a gateway.
+Each autonomous system consists of equipment such as cables (network links),
+routers and switches as well as computers.
+
+The structure of the SimGrid platform description relies exactly on the same
+concept as a real-life platform (see above). Every resource (computers,
+network equipment etc.) belongs to an AS, which can be defined by using the
+\<AS\> tag. Within an AS, the routing between its elements can be defined
+abitrarily. There are several modes for routing, and exactly one mode must be
+selected by specifying the routing attribute in the AS tag:
+
+\verbatim
+<AS id="AS0" routing="Full">
+\endverbatim
+
+\remark
+Other supported values for the routing attribute can be found below, Section
+\ref pf_raf.
+\endremark
+
+There is also the ``<route>`` tag; this tag takes two attributes, ``src`` (source)
+and ``dst`` (destination). Both source and destination must be valid identifiers
+for routers (these will be introduced later). Contained by the ``<route>`` are
+network links; these links must be used in order to communicate from the source
+to the destination specified in the tag. Hence, a route merely describes
+how to reach a router from another router.
+
+\remark
+More information and (code-)examples can be found in the Section \ref pf_rm.
+\endremark
+
+An AS can also contain one or more AS; this allows you to
+define the hierarchy of your platform.
+
+Within each AS, the following types of resources exist:
+\li <b>host</b>: a hostmachine; contains processors/cores etc.