Update doc

doc/sources/admin/download.rst

@@ -5,7 +5,7 @@ Release notes
 -------------
 
 Release notes for latest version:
-https://projects.ow2.org/view/lemonldap-ng/lemonldap-ng-2-0-8-is-out/
+https://projects.ow2.org/view/lemonldap-ng/lemonldap-ng-2-0-9-is-out
 
 Go on https://projects.ow2.org/bin/view/lemonldap-ng/ for older
 versions.
@@ -15,13 +15,13 @@ See also :doc:`upgrade notes<upgrade>`.
 Packages and archives
 ---------------------
 
-Stable version (2.0.8)
+Stable version (2.0.9)
 ~~~~~~~~~~~~~~~~~~~~~~
 
 Tarball
 ^^^^^^^
 
--  `Tarball <https://release.ow2.org/lemonldap/lemonldap-ng-2.0.8.tar.gz>`__
+-  `Tarball <https://release.ow2.org/lemonldap/lemonldap-ng-2.0.9.tar.gz>`__
 
 RPM
 ^^^
@@ -38,17 +38,17 @@ RHEL/CentOS 7
 '''''''''''''
 
 -  `RPM
-   bundle <https://release.ow2.org/lemonldap/lemonldap-ng-2.0.8_el7.rpm.tar.gz>`__
+   bundle <https://release.ow2.org/lemonldap/lemonldap-ng-2.0.9_el7.rpm.tar.gz>`__
 -  `Source
-   RPM <https://release.ow2.org/lemonldap/lemonldap-ng-2.0.8-1.el7.src.rpm>`__
+   RPM <https://release.ow2.org/lemonldap/lemonldap-ng-2.0.9-1.el7.src.rpm>`__
 
 RHEL/CentOS 8
 '''''''''''''
 
 -  `RPM
-   bundle <https://release.ow2.org/lemonldap/lemonldap-ng-2.0.8_el8.rpm.tar.gz>`__
+   bundle <https://release.ow2.org/lemonldap/lemonldap-ng-2.0.9_el8.rpm.tar.gz>`__
 -  `Source
-   RPM <https://release.ow2.org/lemonldap/lemonldap-ng-2.0.8-1.el8.src.rpm>`__
+   RPM <https://release.ow2.org/lemonldap/lemonldap-ng-2.0.9-1.el8.src.rpm>`__
 
 Debian
 ^^^^^^
@@ -67,7 +67,7 @@ Debian
 
 
 -  `DEB
-   bundle <https://release.ow2.org/lemonldap/lemonldap-ng-2.0.8_deb.tar.gz>`__
+   bundle <https://release.ow2.org/lemonldap/lemonldap-ng-2.0.9_deb.tar.gz>`__
 
 Docker
 ^^^^^^

doc/sources/admin/features.rst

@@ -14,13 +14,13 @@ LL::NG is designed using `Model–View–Controller software
 architecture <http://en.wikipedia.org/wiki/Model%E2%80%93View%E2%80%93Controller>`__,
 so you just have to
 :doc:`change HTML/CSS files<portalcustom>` to
-custom portal.
+customize the portal.
 
 Easy to integrate
 -----------------
 
 :doc:`Integrating applications<applications>` in
-LL::NG is easy since its dialog with applications is based on
+LL::NG is easy since its dialogue with applications is based on
 :ref:`customizable HTTP headers<headers>`.
 
 Unifying authentications (Identity Federation)
@@ -32,7 +32,7 @@ heterogeneous architecture. LL:NG can be set as Identity provider,
 Service Provider or Protocol Proxy
 (:doc:`LL::NG as federation protocol proxy<federationproxy>`).
 
-Its SOAP API can also be used to dialog directly with your custom
+Its SOAP API can also be used to dialogue directly with your custom
 applications.
 
 Sessions
@@ -48,9 +48,9 @@ opened sessions:
 
 -  by users
 -  by IP *(IPv4 and IPv6)*
--  by date
 -  by double IP (sessions opened by the same user from multiple
    computers)
+-  by date
 
 It can be used to delete a session
 
@@ -61,7 +61,7 @@ Session restrictions
 
 By default, a user can open several
 :doc:`sessions<sessions>`. LL::NG can restrict
-this:
+the following:
 
 -  Allow only one session per user
 -  Allow only one IP address per user
@@ -78,11 +78,11 @@ LL::NG can be configured to provides
 -  one secured (SSL only) for sensitive applications
 -  one unsecured for other applications
 
-So if the http cookie is stolen, sensitive applications stay secured.
+So that if the http cookie is stolen, sensitive applications remain secured.
 
 Notifications
 -------------
 
-LL::NG can be used to prompt users with a message. This can be used to
-notify right changes,... See
-:doc:`notifications<notifications>` for more.
+LL::NG can be used to notify users with a message when authenticating. This can be used to
+inform of a change in access rights, the publication of a new IT charter, etc. (See
+:doc:`notifications<notifications>` for more details)

doc/sources/admin/quickstart.rst

@@ -69,14 +69,15 @@ or change it, for example for ``mydomain.com``:
       /etc/apache2/sites-available/*
 
 In order to be able to test, update your DNS or your local ``hosts``
-file to map this names to the SSO server IP:
+file to map these names to the SSO server IP:
 
 -  auth.mydomain.com
 -  manager.mydomain.com
 -  test1.mydomain.com
 -  test2.mydomain.com
 
-For example on your local computer (adjust your server IP and test domain)
+For example, you can enter the following command on your local computer: 
+(adjust according to your server IP and test domain)
 
 ::
 
@@ -87,7 +88,11 @@ For example on your local computer (adjust your server IP and test domain)
 Using nip.io (or other DNS wildcard services)
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-If you cannot edit /etc/hosts or your DNS zone, don't give up yet, you can use services such as http://nip.io, http://xip.io, https://sslip.io/, or others.
+If you cannot edit /etc/hosts or your DNS zone, don't give up yet, you can use services such as `nip.io`_, `xip.io`_, `sslip.io`_ or others.
+
+.. _nip.io: http://nip.io/
+.. _xip.io: http://xip.io/
+.. _sslip.io: https://sslip.io
 
 For example, if your server IP is 192.168.12.13, you can use 192-168-12-13.nip.io as your SSO domain: