diff --git a/pom.xml b/pom.xml
index 83a6bb76a1a932f8980e2eea626577bb6b4ec6a1..696db948450f43d4b89d9ed299b3eb681ad54d24 100644
--- a/pom.xml
+++ b/pom.xml
@@ -36,7 +36,7 @@
<rugged.maven-surefire-report-plugin.version>2.18.1</rugged.maven-surefire-report-plugin.version>
<rugged.jgit.buildnumber.version>1.2.8</rugged.jgit.buildnumber.version>
<rugged.plantuml.version>7999</rugged.plantuml.version>
- <rugged.orekit.version>7.1-SNAPSHOT</rugged.orekit.version>
+ <rugged.orekit.version>7.1</rugged.orekit.version>
<rugged.apache-commons-math.version>3.6</rugged.apache-commons-math.version>
<rugged.compiler.source>1.6</rugged.compiler.source>
<rugged.compiler.target>1.6</rugged.compiler.target>
diff --git a/src/site/markdown/design/overview.md b/src/site/markdown/design/overview.md
index 6ec14558941c4d8191f18e99cd052aecb650c03b..a33ccbea545ce27b6a680530c60e01cc037191b3 100644
--- a/src/site/markdown/design/overview.md
+++ b/src/site/markdown/design/overview.md
@@ -67,7 +67,7 @@ The following table sorts out the various topics between the various layers.
| IERS data correction | Orekit |All frame transforms support the full set of IERS Earth Orientation Parameters corrections, including of course the large DUT1 time correction, but also the smaller corrections to older IAU-76/80 or newer IAU-2000/2006 precession nutation models as well as the polar wander. The frames level accuracy is at sub-millimeter level
| Grid-post elevation model | Rugged |Only raster elevation models are supported
|Triangulated Irregular Network elevation model | Not supported |If vector elevation models are needed, they must be converted to raster form in order to be used
-| Geoid computation | Not in version 1 |The first version only supports Digital Elevation Models computed with respect to a reference ellipsoid. If needed, this feature could be added after version 1, either at Rugged or Orekit level, using Orekit gravity fields
+| Geoid computation | Orekit |Rugged expects the Digital Elevation Models to be provided with respect to a reference ellipsoid. Orekit can be used to convert a geoid-based DEM to an ellipsoid-based DEM, directly from any gravity field
| Time-dependent deformations | Interface/Rugged |Simple line-of-sight models (typically polynomial) can be used
| Calibration |Image processing or interface|The calibration phase remains at the mission-specific caller level (pixels geometry, clock synchronization …), the caller is required to provide the already calibrated line of sights
| DEM file parsing | Interface |The elevation models are dedicated to the mission and there are several formats (DTED, GeoTIFF, raw data …).Rugged only deals with raw elevation on small latitude/longitude cells
diff --git a/src/site/markdown/faq.md b/src/site/markdown/faq.md
index 87c7b224a9a0d03635776922ac057d94bc19753f..3384a20578712a21ffa57f182ceb63e78980896f 100644
--- a/src/site/markdown/faq.md
+++ b/src/site/markdown/faq.md
@@ -17,10 +17,8 @@ References
### Has Rugged already been used?
-Almost, as it is used in a project under development.
-
-The first operational use of Rugged will be Sentinel 2 ESA mission.
-Rugged is used in the Image Processing Facility.
+Yes. Rugged is used operationally in the Image Processing Facility
+of the Sentinel 2 ESA mission, which was launched in June 2015.
### Is Rugged validated?
@@ -73,17 +71,13 @@ often seen very early and is the first one unsuspecting users experience. It oft
to configure Orekit to load data.
Configuring data loading is explained in the configuration page For a start, the simplest configuration
-is to download the orekit-data.zip file from the download page and to either set the "orekit.data.path" Java
-property to this file or to manually configure the DataProvidersManager to use it. This example archive file
-contains the required UTC-TAI history file among others. Configuring Orekit to use this archive file can be done
-by keeping the file as a zip archive and pointing to this archive, or by unzipping it and pointing to the unzipped folder.
-
-Here is an example using the file in zip format:
-
- DataProvidersManager.getInstance().addProvider(new ZipJarCrawler(new File("/path/to/the/zip/file/orekit-data.zip")));
-
-Here is an example using the folder resulting from expanding the archive:
+is to download the orekit-data.zip file from the Orekit project download page, to unzip it anywhere you
+want, note the path of the orekit-data folder that will be created and add the following lines at the start
+of your program:
- DataProvidersManager.getInstance().addProvider(new DirectoryCrawler(new File("/path/to/the/folder/orekit-data")));
+ File orekitData = new File("/path/to/the/folder/orekit-data");
+ DataProvidersManager manager = DataProvidersManager.getInstance();
+ manager.addProvider(new DirectoryCrawler(orekitData));
-Using a folder allows one to change the data in it, e.g., adding new EOP files as they are published by IERS.
+Using a folder allows one to change the data in it after the initial download, e.g., adding new EOP files as they
+are published by IERS.
diff --git a/src/site/resources/images/rugged-architecture.png b/src/site/resources/images/rugged-architecture.png
index a6c3cf550324459a2addc565e76c136d2e6f4572..14fb820aca1fb1fc238887d2093016f40005257a 100644
Binary files a/src/site/resources/images/rugged-architecture.png and b/src/site/resources/images/rugged-architecture.png differ