adjusting documentation info about audience

Author: blankdots

docs/instructions.rst

@@ -83,19 +83,25 @@ The configuration variables reside in the same `CONFIG_FILE` as described above
    :language: python
    :lines: 90-116
 
-``server`` should point to an API that returns a public key which can be used to validate the received Bearer token.
-``issuers`` is a string of comma separated values, e.g. `one,two,three` without spaces. The issuers string contains
-a list of entities that are viewed as trusted organisations.
-``bona_fide`` should point to an API that returns the `bona_fide_status` this is
-`ELIXIR AAI <https://www.elixir-europe.org/services/compute/aai>`_ specific.
-``audience`` is a string of comma separated values, e.g. `aud1,aud2,aud3` of intended audiences. Audience is a value
-in JWT that describes what service(s) the token is intended for. You can get an audience hash or URI from the AAI service
-your application is using, or if your service is part of a Beacon Network, you can get the key from your Beacon Network administrator.
-Leave this empty if your service doesn't care about the intended audience.
+* ``server`` should point to an API that returns a public key, which can be used to validate the received JWTBearer token.
+* ``issuers`` is a string of comma separated values, e.g. `one,two,three` without spaces. The issuers string should contain
+  a list of entities that are viewed as trusted organisations.
+* ``bona_fide`` should point to an API that returns the `bona_fide_status` this is
+  `ELIXIR AAI <https://www.elixir-europe.org/services/compute/aai>`_ specific.
+* ``audience`` is a string of comma separated values, e.g. ``aud1,aud2,aud3`` of intended audiences. Audience is a value
+  in JWT that describes what service(s) the token is intended for. 
+
+The audience `hash` or `URI` from the AAI service can be used, or if the service is part of a `Beacon Network`, 
+use the key provided by the Beacon Network administrator.
+
+**Leave empty if the service doesn't care about the intended audience.**
+
 ``verify_aud`` can be set to either ``True`` or ``False``. If enabled, this option forces Beacon to verify the audience(s)
-in the supplied token. If disabled, the audience(s) of a token will not be validated. Disabling this can be a good solution for standalone
-Beacons, that want to be able to use tokens generated by any authority. If you set ``verify_aud=True`` be sure
-to also set a value for ``audience`` key, as otherwise the audience will be attempted to be valited, but as no audiences
+in the supplied token. If disabled, the audience(s) of a token will not be validated. 
+
+Disabling this can be a good solution for standalone
+Beacons, that want to be able to use tokens generated by any authority. If ``verify_aud=True`` is set
+provide also value(s) for ``audience`` key, as otherwise the audience will be attempted to be valited, but as no audiences
 are listed, the validation will fail.
 
 .. note:: For implementing `CONTROLLED` dataset permissions see :ref:`permissions`.