wip

docs/api_docs/services/catalog/create_sensors.rst

@@ -189,7 +189,7 @@ request (componentType, componentDesc and location).
 Adding several sensors
 ~~~~~~~~~~~~~~~~~~~~~~
 
-In case it is necessary to add a serie of sensors, the request will be
+In case it is necessary to add a set of sensors, the request will be
 very similar to the previous one, modifying the message body:
 
 ::
@@ -224,7 +224,7 @@ in the body message
 In this case, instead of registering a single sensor, there will be
 added two new sensors associated with the component named METEO-1. If
 the component does not yet exist in the system, will be registered with
-the properties especified in the request (type and localtzació).
+the properties specified in the request (type and location).
 
 Adding one sensor with additional info
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

docs/api_docs/services/subscription/subscription.rst

@@ -161,7 +161,7 @@ Notifications to untrusted HTTPS
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 In case that remote endpoint uses a self-signed certificate, add the
-following configuration in the config.properties of the
+following configuration in the :literal:`config.properties` of the
 sentilo-platform-server:
 
 ::

docs/architecture.rst

@@ -247,9 +247,9 @@ layer:
 
 -  Redis is responsible for sending the published information to
    ListenerMessageContainer event, who is responsible for managing the
-   subscription in Redis as a client for any type of event. \**(*)*\*
+   subscription in Redis as a client for any type of event.
 -  The container notifies the event to each subscription associated with
-   it sending a request, via HttpCallback \**(*)*\*
+   it sending a request, via :literal:`HttpCallback`
 
 The platform registers a task that runs periodically who is responsible
 for credentials & permissions synchronization, stored in memory in

docs/catalog_and_maps/administration_console.rst

@@ -279,7 +279,7 @@ where:
 -  the *Permissions*\ tab allows to manage the permissions for other
    entities (applications or providers)
 -  the *Active subscriptions* tab displays a list with all the active
-   subscriptions for the current application (from version 1.5).
+   subscriptions for the current application.
 
 The main properties of the *Details* tab are the following:
 
@@ -464,7 +464,7 @@ where
 -  The *Sensors/Actuators* tab displays a list with all sensors owned by
    the current provider (i.e. associated with this provider).
 -  The *Components* tab displays a list with all components owned by the
-   current provider (from version 1.5).
+   current provider.
 -  The *Active subscriptions* tab displays a list with all the active
    subscriptions for the current provider.
 -  The *Documentation* In this tab you can upload any files relevant to
@@ -1366,13 +1366,13 @@ Example of dashboard:
    The page will show graphics for this time. If you reload the page, the history will be reset.
 
 New internal monitor API runs on different port that the Sentilo API. It's port number is configured in
-/sentilo-platform/sentilo-platform-server/src/main/resources/properties/config.properties. The default value is 7081.
+:literal:`/sentilo-platform/sentilo-platform-server/src/main/resources/properties/config.properties`. The default value is 7081.
 
 ..
 
-   monitor.port=7081
+    monitor.port=7081
 
-The agent `Metrics Monitor Agent <./integrations.html#metrics-monitor-agent>`__ gathers these metrics and persists them in Elasticsearch.
+The agent `Metrics Monitor Agent </integrations.html#metrics-monitor-agent>`__ gathers these metrics and persists them in Elasticsearch.
 
 
 .. |ComponentsTypes.png| image:: ../_static/images/catalog_and_maps/ComponentsTypes.png

docs/catalog_and_maps/map_viewers.rst

@@ -122,7 +122,7 @@ Map Providers
 For all background maps, you can use either Google or Leaflet map provider. Through the latter you can consume
 any OGC WMS/WMTS service that provides a EPSG 3857 SRID.
 
-The configuration of both is in in /sentilo-catalog-web/src/main/resources/properties/catalog-config.properties.
+The configuration of both is in in :literal:`/sentilo-catalog-web/src/main/resources/properties/catalog-config.properties`.
 
 Example of Google Maps configuration
 

docs/clients/java_client.rst

@@ -61,8 +61,8 @@ Now you can then navigate into the project and edit the source code.
 The properties file
 ^^^^^^^^^^^^^^^^^^^
 
-You must modify the properties file **application.properties** located
-in **src/main/resources/properties** in order to provide your correct
+You must modify the properties file :literal:`application.properties` located
+in :literal:`src/main/resources/properties` in order to provide your correct
 Sentilo Platform Client configurations. There’re some values that are
 for testing purposes, and they may not be changed.
 

docs/clients/raspberrypi_client.rst

@@ -798,7 +798,7 @@ Debugging the library
 ^^^^^^^^^^^^^^^^^^^^^
 
 If you need to debug your execution, you can edit the file
-**/sentiloclient/utils/SentiloLogs.js** and edit the logs configuration
+:literal:`/sentiloclient/utils/SentiloLogs.js` and edit the logs configuration
 properties, as you need:
 
 ::

docs/integrations.rst

@@ -136,7 +136,7 @@ this page.
 **Configuration**
 
 Activity Monitor Agent is configured with a set of .properties files in
-*sentilo/sentilo-agent-activity-monitor/src/main/resources/properties*.
+:literal:`sentilo/sentilo-agent-activity-monitor/src/main/resources/properties`.
 
 **subsription.properties**
 
@@ -224,7 +224,7 @@ datasources.
 **Configuration**
 
 Historian Agent is configured with a set of .properties files in
-sentilo/sentilo-agent-historian/src/main/resources/properties.
+:literal:`sentilo/sentilo-agent-historian/src/main/resources/properties`.
 
 **subsription.properties**
 
@@ -316,7 +316,7 @@ to forward the events to this endpoint URL.
 **Configuration**
 
 Federation Agent's configuration is in file
-sentilo/sentilo-agent-federation/src/main/resources/properties/application.properties.
+:literal:`sentilo/sentilo-agent-federation/src/main/resources/properties/application.properties`.
 
 +---------------------------------------------+---------------------------------------+----------------------------------------------------------------------------------------------------------+
 | Property                                    | Default Value                         | Description                                                                                              |
@@ -434,7 +434,7 @@ and it's same as for the `Activity Monitor Agent`_. Example configuration:
     batch.max.retries=1
 
 
-The difference with the Activity Monitor agent is the Redis topic in subscription.properties:
+The difference with the Activity Monitor agent is the Redis topic in :literal:`subscription.properties`:
 
 ..
 

docs/setup.rst

@@ -145,7 +145,7 @@ machine and listening in the following ports:
 -  openTSDB: 4242
 
 All these settings can be found in the subdirectory
-**/src/main/resources/properties** of each platform’s module.
+:literal:`/src/main/resources/properties` of each platform’s module.
 
 Redis settings
 ~~~~~~~~~~~~~~
@@ -237,7 +237,7 @@ command from the directory where the file is located:
    recommend to change them before installing Sentilo in a production
    environment.
 
-If you change default values in the /sentilo/scripts/mongodb/init_data.js file and load them to
+If you change default values in the :literal:`/sentilo/scripts/mongodb/init_data.js` file and load them to
 MongoDB, you will have to modify the following properties before compiling and building Sentilo. So, following
 JS code from *init_data.js* :
 

docs/technical_faq.rst

@@ -43,7 +43,7 @@ Recently Google changed it policy regarding Maps key. Please go to
 https://developers.google.com/maps/documentation/javascript/get-api-key
 and create one.
 
-You can define the API key inside the sentilo/sentilo-catalog-web/src/main/resources/properties/catalog-config.properties configuration file:
+You can define the API key inside the :literal:`sentilo/sentilo-catalog-web/src/main/resources/properties/catalog-config.properties` configuration file:
 
 .. code:: properties