docs: fix a sphinx formatting error

[simgrid.git] / docs / source / Introduction.rst

diff --git a/docs/source/Introduction.rst b/docs/source/Introduction.rst
index 4102473b546ef9dfcce7728060951c921f121476..27dab2e09108503e44ec47aa741a4dd4d223c74c 100644 (file)
--- a/docs/source/Introduction.rst
+++ b/docs/source/Introduction.rst
@@ -24,12 +24,12 @@ Any SimGrid study entails the following components:
 
  - The **simulated platform**. This is a description of a given
    distributed system (machines, links, disks, clusters, etc). Most of
 
  - The **simulated platform**. This is a description of a given
    distributed system (machines, links, disks, clusters, etc). Most of

-   the platform files are written in XML although a Lua interface is
-   under development.  SimGrid makes it easy to augment the Simulated
-   Platform with a Dynamic Scenario where for example the links are
-   slowed down (because of external usage) or the machines fail. You
-   even have support to specify the applicative workload that you want
-   to feed to your application
+   the platform files are written in XML but a new C++ programmatic
+   interface has recently been introduced. SimGrid makes it easy to
+   augment the Simulated Platform with a Dynamic Scenario where for
+   example the links are slowed down (because of external usage) or the
+   machines fail. You even have support to specify the applicative
+   workload that you want to feed to your application

    :ref:`(more info) <platform>`.
 
  - The application's **deployment description**. In SimGrid
    :ref:`(more info) <platform>`.
 
  - The application's **deployment description**. In SimGrid


@@ -84,7 +84,7 @@ To ease such questioning, you really should logically separate these
 parts in your experimental setup. It is seen as a very bad practice to
 merge the application, the platform, and the deployment altogether.
 SimGrid is versatile and your mileage may vary, but you should start
 parts in your experimental setup. It is seen as a very bad practice to
 merge the application, the platform, and the deployment altogether.
 SimGrid is versatile and your mileage may vary, but you should start

-with your Application specified as a C++ or Java program, using one of
+with your Application specified as a C++ or Python program, using one of

 the provided XML platform files, and with your deployment in a separate
 XML file.
 
 the provided XML platform files, and with your deployment in a separate
 XML file.