lib: location: Update documentation

Added a limitation in the library documentation. GNSS API should
not be used directly by the application when Location library is used.
Doing so may lead to unexpected behavior, because GNSS may be in
a different state than expected by the library.

Signed-off-by: Tommi Kangas <[email protected]>

Author: tokangas

doc/nrf/libraries/modem/location.rst

@@ -32,7 +32,7 @@ The supported location methods are as follows:
 
 * GNSS positioning
 
-  * Uses :ref:`gnss_interface` for getting the location.
+  * Uses :ref:`GNSS interface<gnss_interface>` for getting the location.
   * A-GNSS and P-GPS are managed with :ref:`lib_nrf_cloud_agnss` and :ref:`lib_nrf_cloud_pgps`.
   * The application may also use some other source for the data and use :c:func:`location_agnss_data_process` and :c:func:`location_pgps_data_process` to pass the data to the Location library.
   * The data format of A-GNSS or P-GPS must be as received from :ref:`lib_nrf_cloud_agnss`.
@@ -379,7 +379,10 @@ The following |NCS| applications and samples use this library:
 Limitations
 ***********
 
-* The Location library can only have one application registered at a time. If there is already an application handler registered, another initialization will override the existing handler.
+* The Location library can only have one application registered at a time.
+  If there is already an application handler registered, another initialization will override the existing handler.
+* The :ref:`GNSS interface<nrfxlib:gnss_interface>` should not be used directly by the application when using the Location library.
+  Using the GNSS interface from both the application and the Location library may lead to unexpected behavior.
 
 Dependencies
 ************
@@ -397,7 +400,7 @@ This library uses the following |NCS| libraries:
 
 It uses the following `sdk-nrfxlib`_ library:
 
-* :ref:`nrfxlib:gnss_interface`
+* :ref:`GNSS interface<nrfxlib:gnss_interface>`
 
 It uses the following Zephyr libraries: