doc: Doc checks for 2.3.0 release

umapraseeda · tmon-nordic · commit be94cc3f090d · 2023-02-21T12:35:24.000+01:00
doc checks for 2.3 release

Signed-off-by: Uma Praseeda &lt;uma.praseeda@nordicsemi.no&gt;
diff --git a/doc/links.txt b/doc/links.txt
@@ -44,6 +44,8 @@
 
 .. _`nRF Trace collector`: https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_trace_collector%2FUG%2Ftrace_collector%2Fintro.html
 
+.. _`coex interface of nRF9160`:  https://infocenter.nordicsemi.com/index.jsp?topic=%2Fps_nrf9160%2Fip%2Fradio_lte%2Fdoc%2Fmagpio_if.html
+
 .. ### Source: www.nordicsemi.com
 
 .. _`nRF9160 modem firmware zip file`: https://www.nordicsemi.com/Products/Low-power-cellular-IoT/nRF9160/Download#0B34B59935AF4AFCB7AB93E9646C1F53
@@ -79,6 +81,6 @@
 
 .. _`NMEA report sample`: http://aprs.gids.nl/nmea/#gsa
 
-.. _`Bluetooth Core Specification`: https://www.bluetooth.com/specifications/specs/core-specification/
+.. _`Bluetooth Core Specification`: https://www.bluetooth.com/specifications/specs/core-specification-5-4/
 
 .. _`Appropriate Language Mapping Table`: https://www.bluetooth.com/language-mapping/Appropriate-Language-Mapping-Table
diff --git a/lc3/CHANGELOG.rst b/lc3/CHANGELOG.rst
@@ -3,6 +3,10 @@
 Changelog
 #########
 
+.. contents::
+   :local:
+   :depth: 2
+
 All notable changes to this project are documented on this page.
 
 nRF Connect SDK v2.2.0
diff --git a/mpsl/doc/bluetooth_coex.rst b/mpsl/doc/bluetooth_coex.rst
@@ -96,7 +96,7 @@ Interface
 **********
 
 The 1-wire protocol lets Bluetooth LE nRF chips coexist alongside an LTE device on a separate chip.
-It was specifically designed for the `coex interface of nRF9160 <https://infocenter.nordicsemi.com/index.jsp?topic=%2Fps_nrf9160%2Fip%2Fradio_lte%2Fdoc%2Fmagpio_if.html>`_.
+It was specifically designed for the `coex interface of nRF9160`_.
 
 
 Hardware resources
diff --git a/nfc/CHANGELOG.rst b/nfc/CHANGELOG.rst
@@ -9,7 +9,7 @@ Changelog
 
 All notable changes to this project are documented in this file.
 
-main branch
+Main branch
 ***********
 
 Added
diff --git a/nrf_modem/doc/at_interface.rst b/nrf_modem/doc/at_interface.rst
@@ -87,7 +87,7 @@ The following snippet shows how to use :c:func:`nrf_modem_at_printf` to send a f
 	}
 
 Any return value other than zero indicates an error.
-Negative values indicate that the Modem library has failed to send the AT command, and they represent a nrf_errno code that indicates the reason for the failure.
+Negative values indicate that the Modem library has failed to send the AT command, and they represent an ``nrf_errno`` code that indicates the reason for the failure.
 Positive values indicate that the modem has received the AT command and has responded with an error.
 When a positive value is returned, the error type can be retrieved using the :c:func:`nrf_modem_at_err_type` helper function, and the error value (in case of CME or CMS errors) can be retrieved with the :c:func:`nrf_modem_at_err` helper function.
 
diff --git a/nrf_modem/doc/delta_dfu.rst b/nrf_modem/doc/delta_dfu.rst
@@ -34,7 +34,7 @@ Limitations
 
 The size of the scratch area can be retrieved with the :c:func:`nrf_modem_delta_dfu_area` function, which returns the size of the area in bytes.
 A limitation of delta updates is that the size of the update must not exceed the area of flash memory that a given modem firmware version has dedicated for this operation.
-The size of this area varies for any given modem firmware version and it can be retrieved with the Modem library :c:func:`nrf_modem_delta_dfu_area` function.
+The size of this area varies for any given modem firmware version and it can be retrieved with the Modem library's :c:func:`nrf_modem_delta_dfu_area` function.
 In general, this function can be useful when the size of the largest delta update that can be received needs to be reported to an external service, for example an LwM2M server.
 In practice, the application does not use this function in the normal update process, since all delta update files that are part of the `nRF9160 modem firmware zip file`_ are guaranteed to fit in the scratch area of the modem firmware version that they apply to.
 
diff --git a/nrf_modem/doc/fault_handling.rst b/nrf_modem/doc/fault_handling.rst
@@ -3,6 +3,10 @@
 Modem fault handling
 ####################
 
+.. contents::
+   :local:
+   :depth: 2
+
 The application core and the modem core are separate cores on the nRF9160 SiP.
 When the modem core on the nRF9160 SiP crashes, it sends a fault signal to the application core.
 
@@ -43,7 +47,7 @@ Socket APIs that require communication with the modem, return ``-1`` and set ``e
 Although the modem has crashed, any data which was stored by the Modem library, including data that was delivered to the Modem library by the modem, remains available until the Modem library is shut down.
 This includes incoming network data, which was received before the crash but has not been read by the application.
 The application can read that data as normal, using the :c:func:`recv` function.
-When no more data is available, the :c:func:`recv` returns ``-1`` and sets ``errno`` to ``NRF_ESHUTDOWN``.
+When no more data is available, the :c:func:`recv` function returns ``-1`` and sets ``errno`` to ``NRF_ESHUTDOWN``.
 
 Ongoing API calls
 *****************
diff --git a/nrf_modem/doc/sockets.rst b/nrf_modem/doc/sockets.rst
diff --git a/nrf_modem/include/nrf_modem_os.h b/nrf_modem/include/nrf_modem_os.h
@@ -96,7 +96,7 @@ void nrf_modem_os_busywait(int32_t usec);
  *
  * @param context Library context.
  * @param[in, out] timeout Timeout in milliseconds, or @c NRF_MODEM_OS_FOREVER for no timeout.
- *			   Specifies the timeout value on input and the remainig
+ *			   Specifies the timeout value on input and the remaining
  *			   time to sleep on output.
  *
  * @retval 0 The thread is woken before the timeout expired.
diff --git a/softdevice_controller/limitations.rst b/softdevice_controller/limitations.rst
@@ -6,9 +6,9 @@ Limitations
 When working with the SoftDevice Controller, you should be aware of the following limitations.
 In addition, see :ref:`nrf:known_issues` for temporary issues that will be fixed in future releases.
 
-DRGN-17562: One of the LE Transmit Power Reporting Event may not be reported to the host.
+DRGN-17562: One of the LE Transmit Power Reporting Events might not be reported to the host.
   When multiple LE Transmit Power Reporting Events are generated at the same time for the same PHY, one of these events will be missed.
-  This will only occur when there are simultaneous remote and local power level changes on the same PHY.
+  This will occur only when there are simultaneous remote and local power level changes on the same PHY.
 
 YOPAN-87: The RSSI value reported by the SoftDevice Controller requires additional temperature compensation
   The RSSI value reported by the SoftDevice Controller is the raw value from the radio peripheral.
diff --git a/zboss/development/include/zcl/zb_zcl_ota_upgrade.h b/zboss/development/include/zcl/zb_zcl_ota_upgrade.h
@@ -1056,7 +1056,7 @@ enum zb_zcl_ota_upgrade_image_block_fc_e
     @param data_size_max - Maximum data size
     @param node_addr - Request node address
     @param block_delay - BlockRequestDelay
-    @param current_delay - Delay current send (millisec)
+    @param current_delay - Delay current send (milliseconds)
 */
 #define ZB_ZCL_OTA_UPGRADE_SEND_IMAGE_BLOCK_REQ(                            \
     buffer, addr, dst_addr_mode, dst_ep, ep, prfl_id, def_resp, cb,         \
diff --git a/zboss/production/include/zcl/zb_zcl_ota_upgrade.h b/zboss/production/include/zcl/zb_zcl_ota_upgrade.h
@@ -1056,7 +1056,7 @@ enum zb_zcl_ota_upgrade_image_block_fc_e
     @param data_size_max - Maximum data size
     @param node_addr - Request node address
     @param block_delay - BlockRequestDelay
-    @param current_delay - Delay current send (millisec)
+    @param current_delay - Delay current send (milliseconds)
 */
 #define ZB_ZCL_OTA_UPGRADE_SEND_IMAGE_BLOCK_REQ(                            \
     buffer, addr, dst_addr_mode, dst_ep, ep, prfl_id, def_resp, cb,         \

Original file line number	Diff line number	Diff line change
@@ -87,7 +87,7 @@ The following snippet shows how to use :c:func:`nrf_modem_at_printf` to send a f
`87`	`87`	`}`
`88`	`88`
`89`	`89`	`Any return value other than zero indicates an error.`
`90`		`-Negative values indicate that the Modem library has failed to send the AT command, and they represent a nrf_errno code that indicates the reason for the failure.`
	`90`	+Negative values indicate that the Modem library has failed to send the AT command, and they represent an ``nrf_errno`` code that indicates the reason for the failure.
`91`	`91`	`Positive values indicate that the modem has received the AT command and has responded with an error.`
`92`	`92`	When a positive value is returned, the error type can be retrieved using the :c:func:`nrf_modem_at_err_type` helper function, and the error value (in case of CME or CMS errors) can be retrieved with the :c:func:`nrf_modem_at_err` helper function.
`93`	`93`
Original file line number	Diff line number	Diff line change
`@@ -96,7 +96,7 @@ void nrf_modem_os_busywait(int32_t usec);`
`96`	`96`	`*`
`97`	`97`	`* @param context Library context.`
`98`	`98`	`* @param[in, out] timeout Timeout in milliseconds, or @c NRF_MODEM_OS_FOREVER for no timeout.`
`99`		`- * Specifies the timeout value on input and the remainig`
	`99`	`+ * Specifies the timeout value on input and the remaining`
`100`	`100`	`* time to sleep on output.`
`101`	`101`	`*`
`102`	`102`	`* @retval 0 The thread is woken before the timeout expired.`