Skip to content

Commit

Permalink
Remove trailing whitespaces
Browse files Browse the repository at this point in the history
  • Loading branch information
Tempate committed Aug 22, 2023
1 parent 1e67a6e commit 1b530b6
Show file tree
Hide file tree
Showing 4 changed files with 10 additions and 10 deletions.
2 changes: 1 addition & 1 deletion docs/rst/getting_started/project_overview.rst
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ The configuration in *YAML* format is very intuitive and human-readable.
The whole application has been thought to be user-friendly, following a user-oriented design.

* **RUN**: In order to run a |ddsrouter| application, just a *YAML* configuration file is required with the specific
configurations (see section :ref:`DDS Router Configuration <user_manual_configuration>` to check how to configure a DDS Router
configurations (see section :ref:`DDS Router Configuration <user_manual_configuration>` to check how to configure a DDS Router
and see section :ref:`Application Arguments <user_manual_user_interface_application_arguments>`
to check the application supported arguments).
* **INTERACT**: Once the |ddsrouter| application is running, the topics involved in this communication can be
Expand Down
6 changes: 3 additions & 3 deletions docs/rst/user_manual/participants/local_discovery_server.rst
Original file line number Diff line number Diff line change
Expand Up @@ -33,12 +33,12 @@ Configuration

The Local Discovery Server Participant allows users to configure the standard attributes of a Discovery Server.

* To configure the Discovery Server :term:`GuidPrefix`, check the
* To configure the Discovery Server :term:`GuidPrefix`, check the
:ref:`Domain Id <user_manual_configuration_domain_id>` configuration section.
* To configure the Discovery Server listening addresses, check the
* To configure the Discovery Server listening addresses, check the
:ref:`Listening Addresses <user_manual_configuration_listening_addresses>` configuration section.
* To configure the Discovery Server connection addresses to connect to other Discovery Servers,
check the
check the
:ref:`Discovery Server Connection Addresses <user_manual_configuration_discovery_server_connection_addresses>` configuration section.

.. note::
Expand Down
6 changes: 3 additions & 3 deletions docs/rst/user_manual/participants/wan.rst
Original file line number Diff line number Diff line change
Expand Up @@ -35,13 +35,13 @@ Kind aliases
Configuration
=============

The WAN Participant allows users to configure the listening and connection addresses (whether it should locate or
The WAN Participant allows users to configure the listening and connection addresses (whether it should locate or
be located by other remote Participants):

* To configure the listening addresses, check the
* To configure the listening addresses, check the
:ref:`Listening Addresses <user_manual_configuration_listening_addresses>` configuration section.
* To configure the connection addresses to connect with other Wan Participants,
check the
check the
:ref:`Initial Peers Connection Addresses <user_manual_configuration_initial_peers_connection_addresses>` configuration section.

.. note::
Expand Down
6 changes: 3 additions & 3 deletions docs/rst/user_manual/participants/wan_discovery_server.rst
Original file line number Diff line number Diff line change
Expand Up @@ -36,12 +36,12 @@ Configuration

The WAN Discovery Server Participant allows users to configure the standard attributes of a Discovery Server.

* To configure the Discovery Server :term:`GuidPrefix`, check the
* To configure the Discovery Server :term:`GuidPrefix`, check the
:ref:`Domain Id <user_manual_configuration_domain_id>` configuration section.
* To configure the Discovery Server listening addresses, check the
* To configure the Discovery Server listening addresses, check the
:ref:`Listening Addresses <user_manual_configuration_listening_addresses>` configuration section.
* To configure the Discovery Server connection addresses to connect to other Discovery Servers,
check the
check the
:ref:`Discovery Server Connection Addresses <user_manual_configuration_discovery_server_connection_addresses>` configuration section.

.. note::
Expand Down

0 comments on commit 1b530b6

Please sign in to comment.