--- a/src/source/appmanage.rst	Fri Apr 27 14:44:33 2018 +0200
+++ b/src/source/appmanage.rst	Wed May 16 14:03:44 2018 +0200
@@ -10,7 +10,7 @@
 
 When the PyAMS is initialized, it create and register several utilities into the *local registry* and saved into ZODB.
 These utilities are created with default values which can be modified through **management interface** when
-the application is started.
+the application is started by default (http://localhost:6543/admin).
 
 
 Local registry utilities
@@ -21,33 +21,59 @@
 
 Some important utilities include:
 
-- a **catalog**: the catalog has the responsibility to index every content properties which are required to make quick
-  and efficient searches. Catalog indexes are automatically created on database upgrade; management interface
-  allows administrator to get indexes properties, to get the number of indexed objects and values for a given index, and
-  to delete an index before recreating it by running the database upgrade script another time (see :ref:`scripts`).
+**Catalog**:
+    The catalog has the responsibility to index every content properties which are required to make quick
+    and efficient searches. Catalog indexes are automatically created on database upgrade; management interface
+    allows administrator to get indexes properties, to get the number of indexed objects and values for a given index, and
+    to delete an index before recreating it by running the database upgrade script another time (see :ref:`scripts`).
 
-- an **internal IDs** utility:
+**Internal IDs** utility:
+    The catalog object doesn't store direct references to objects, but their internal IDs which are generated by this
+    utility.
 
-- a **language negotiator**:
+**Language negotiator**:
+    As a web site or application can be localized, this utility allows you to define priorities between language
+    definition options (between *user session*, *browser* end *server*), and to define which languages are available
+    to your users (which is particularly important when managing potentially multi-lingual contents).
+
+    .. tip::
+        Static texts like those displayed into PyAMS management interface are always translated to the language defined
+        into browser language, if available.
 
-- a **portal templates** container:
+**Portal templates** container:
+    Portal templates are used to define *presentation templates* based on *portlets* (see :ref:`pyams_portal`). You can
+    create *local* templates, or create *shared templates* into this utility which can then be reused into several
+    places in your web site.
 
-- a **security manager**:
+**Security manager**:
+    This utility is used to define authentication sources which will be available to authenticate your users.
+    :ref:`pyams_security` package provides several authentication modules (like local users, or via OAuth/OAuth2
+    providers); :ref:`pyams_ldap` add authentication plug-in via an LDAP directory.
 
-- a **sequential IDs** utility:
+**Sequential IDs** utility:
+    This utility is used to assign simple sequential IDs to site contents (like sites, news, topics and more); these
+    IDs are simple to identify a given content; several versions of a given content handle by workflow share the same
+    sequential ID.
 
-- a **server timezone** utility:
+**Server timezone** utility:
+    Define the timezone server to display date and time accordingly.
 
-- a **user profiles** container:
+**User profiles** container:
+    This utility is used to store information associated to principals through their user profile.
 
 
 Optional utilities can also include:
 
-- an **Elasticsearch content indexer**:
+**Elasticearch content indexer**:
 
-- a **maps manager**:
+Verifier la connection entre le server ElasticSearch et la l'application PyAMS
 
-- a **medias converter**:
+**Maps manager**:
+Systeme de cartografie, avec OpenStreeMaps, WMS, GeoPortable, ESRI ou encore Google Maps
+permet de créer des zones catographique²
 
-- a **tasks scheduler**:
+**Medias converter**:
+
 
+**Tasks scheduler**:
+