doc: feedback edits

Applying the feedback that was provided.

Signed-off-by: Wille Backman <wille.backman@nordicsemi.no>

Author: wiba-nordic

.gitignore

@@ -12,5 +12,4 @@ __pycache__/
 /twister-out*
 
 # docs
-/doc/_build*
 /docs/_build*

docs/about.rst

@@ -6,17 +6,16 @@ About Zigbee protocol
 .. note::
    .. include:: /includes/experimental_note.txt
 
-The |NCS|'s Zigbee protocol uses the ZBOSS library, a third-party precompiled Zigbee stack.
+The |addon| for the |NCS| uses the ZBOSS library, a third-party precompiled Zigbee stack.
 It includes all mandatory features of the |zigbee_version| specification and provides an Application Programming Interface (API) to access different services.
 The stack comes with the following features:
 
-* Complete implementation of the Zigbee core specification and Zigbee Pro feature set.
+* Complete implementation of the Zigbee core specification and Zigbee Pro feature set, revision 21, 22, and 23.
 * Support for all device roles: Coordinator, Router, and End Device.
-* Zigbee Cluster Library, including :ref:`lib_zigbee_fota`.
-* Base Device Behavior.
-* Device definitions for devices that were implemented for Zigbee Home Automation and Light Link profiles.
+* Zigbee Cluster Library.
+* Base Device Behavior version 3.0.1.
+* Zigbee Cluster Library, revision 8.
 * Zigbee Green Power Proxy Basic.
-* Experimental support for ``ZB_ZCL_WWAH``.
 
 See `Software maturity levels`_ in the |NCS| documentation for what experimental support means.
 Experimental support also means that the feature is either not certified or no sample is provided for the given feature (or both).
@@ -57,7 +56,7 @@ In each topology, the nodes have the following responsibilities:
 * *Zigbee Router* - Extends the range of the network.
   For this reason, the router has the radio enabled at all times.
   However, in the star topology it is not moving packets through the network.
-* *Zigbee End Device* - Receives messages from the parent device, in this case the coordinator.
+* *Zigbee End Device* - Receives messages from the parent device.
 
 In every Zigbee topology, each router and end device that joins the Zigbee network after its creation by the coordinator needs a parent device.
 When a device wants to join the network, it sends a beacon request to scan for available devices.
@@ -67,7 +66,7 @@ Based on different factors of responses, such as signal strength, the new device
 For end devices, the parent device (a coordinator or a router) can store information meant for them.
 This is required because the end devices do not receive packets directly from other devices.
 Each packet meant for an end device needs to go through its parent, and the end devices need to regularly request and respond to packets from the parents.
-For example, in the |NCS|, the Zigbee light switch device requests packets from the parent every three seconds.
+For example, in the |addon| for the |NCS|, the Zigbee light switch device requests packets from the parent every three seconds.
 The end device does not route packets.
 It can also disable its radio to reduce the power consumption between the regular packet requests if the Sleepy End Device behavior is enabled.
 
@@ -76,7 +75,7 @@ Additional information
 
 If you want to learn more about the Zigbee topics and terminology mentioned in this guide, read the following pages:
 
-* :ref:`ug_zigbee_architectures` page to learn more about the Zigbee architecture available in the |NCS|.
+* :ref:`ug_zigbee_architectures` page to learn more about the Zigbee architecture.
 * `Common ZCL terms and definitions`_ section in the ZBOSS user guide.
 * Zigbee topologies in section 1.1.4 of the `Zigbee Specification <CSA Specifications Download Request_>`_.
 * :ref:`zigbee_ug_sed` section on the :ref:`ug_zigbee_configuring` page.

docs/adding_clusters.rst

@@ -6,9 +6,7 @@ Adding ZCL clusters to application
 ##################################
 
 .. note::
-   The contents of this user guide are inaccurate and will be updated in one of the upcoming releases.
-   The information about the update will be posted in the release notes.
-   For the time being, do not use this guide.
+   .. include:: /includes/experimental_note.txt
 
 .. contents::
    :local:
@@ -372,19 +370,20 @@ Complete the following steps to read the cluster list of a Zigbee node:
 Further expanding the custom application
 ****************************************
 
-You can further expand the application with more features, such as OTA support.
+You can further expand the application with more features.
 
-.. _ug_zigee_adding_clusters_ota:
+..
+  .. _ug_zigee_adding_clusters_ota:
 
-Adding OTA
-==========
+  Adding OTA
+  ==========
 
-To extend the sample with OTA support, we would have to complete steps similar to :ref:`adding On/Off Switch and Temperature Sensor functionalities <ug_zigee_adding_clusters_adding_clusters>`.
-Then, we would have to implement the ZCL device callback to control the process of collecting chunks of new firmware.
-This is described more broadly in the following sections.
+  To extend the sample with OTA support, we would have to complete steps similar to :ref:`adding On/Off Switch and Temperature Sensor functionalities <ug_zigee_adding_clusters_adding_clusters>`.
+  Then, we would have to implement the ZCL device callback to control the process of collecting chunks of new firmware.
+  This is described more broadly in the following sections.
 
-Fortunately, we can use the :ref:`lib_zigbee_fota` library to handle the majority of these implementation steps.
-To add OTA support to the extended application, follow the steps in :ref:`ug_zigbee_configuring_components_ota`.
+  Fortunately, we can use the :ref:`lib_zigbee_fota` library to handle the majority of these implementation steps.
+  To add OTA support to the extended application, follow the steps in :ref:`ug_zigbee_configuring_components_ota`.
 
 
 .. _ug_zigee_adding_clusters_passing_events:

docs/architectures.rst

@@ -7,17 +7,22 @@ Architectures
    :local:
    :depth: 2
 
-This page describes the platform designs that are possible with the Zigbee stack on Nordic Semiconductor devices.
+.. note::
+   .. include:: /includes/experimental_note.txt
+
+This page describes the platform designs that are possible with the Zigbee stack on the nRF54L15 development kit.
 
 The designs are described from the least to the most complex, that is from simple applications that consist of a single chip running single or multiple protocols to scenarios in which the nRF SoC acts as a network co-processor when the application is running on a much more powerful host processor.
 
+.. include:: /includes/coprocessor_note.txt
+
 .. _ug_zigbee_platform_design_soc:
 
 System-on-Chip designs
 **********************
 
-This single-chip solution has the combined RFIC (the IEEE 802.15.4 in case of Zigbee) and processor.
-The Zigbee stack and the application layer run on the local processor.
+The single-chip solution has a combined RFIC (the IEEE 802.15.4 in case of Zigbee) and processor.
+Both the Zigbee stack and the application layer run on the local processor.
 
 This design has the following advantages:
 
@@ -27,7 +32,7 @@ This design has the following advantages:
 
 It also has the following disadvantages:
 
-* For some uses, the nRF SoC's MCU can be to slow to handle both the application and the network stack load.
+* For some uses, the nRF SoC's MCU can be too slow to handle both the application and the network stack load.
 * The application and the network stack share flash and RAM space.
   This leaves less resources for the application.
 * Dual-bank DFU or an external flash is needed to update the firmware.
@@ -71,7 +76,7 @@ It also has the following disadvantages:
 .. figure:: images/zigbee_platform_design_multi.svg
    :alt: Multiprotocol Zigbee and Bluetooth LE architecture (nRF54L Series devices)
 
-   Multiprotocol Zigbee and Bluetooth LE architecture on nRF52 Series devices
+   Multiprotocol Zigbee and Bluetooth LE architecture on nRF54L Series devices
 
 ..
   .. figure:: images/zigbee_platform_design_nRF5340_multi.svg
@@ -90,6 +95,8 @@ This platform design is suitable for the following development kit:
 Co-processor designs
 ********************
 
+.. include:: /includes/coprocessor_note.txt
+
 In co-processor designs, the application runs on one processor (the host processor) and communicates with another processor that provides the radio interface.
 In these designs, the more powerful processor (host) interacts with the Zigbee network through a connectivity device, for example a Nordic Semiconductor's device with the Zigbee interface.
 
@@ -123,15 +130,17 @@ It also has the following disadvantages:
 
    Split Zigbee architecture
 
-The |NCS| includes the :ref:`ug_zigbee_tools_ncp_host` tool.
-|zigbee_ncp_package|
+..
+  The |addon| for the |NCS| includes the :ref:`ug_zigbee_tools_ncp_host` tool.
+  |zigbee_ncp_package|
 
-The tool is available for download as a standalone :file:`zip` package using the following link:
 
-* `ZBOSS NCP Host`_ (|zigbee_ncp_package_version|)
+  The tool is available for download as a standalone :file:`zip` package using the following link:
 
-|zigbee_ncp_package_more_info|
+    * `ZBOSS NCP Host`_ (|zigbee_ncp_package_version|)
 
-This platform design is suitable for the following development kits:
+    |zigbee_ncp_package_more_info|
+
+  This platform design is suitable for the following development kits:
 
-.. include:: /includes/device_table_ncp.txt
+  .. include:: /includes/device_table_ncp.txt

docs/commissioning.rst

@@ -7,11 +7,14 @@ Commissioning
    :local:
    :depth: 2
 
+.. note::
+   .. include:: /includes/experimental_note.txt
+
 Commissioning is a process that allows a new Zigbee device to join a Zigbee network.
 The device is configured into the network, so that it can start communicating with other network nodes.
 If there is no network to join, the commissioning procedure ensures that a new network is created.
 
-You can configure Zigbee commissioning in the |NCS| by setting parameters before the start of the :ref:`zigbee_zboss`.
+You can configure Zigbee commissioning by setting parameters before the start of the :ref:`zigbee_zboss`.
 For more information, see the `Support for Zigbee commissioning`_ section in the ZBOSS stack documentation.
 
 .. _zigbee_commissioning_start:
@@ -32,7 +35,7 @@ In the ZBOSS stack, the commissioning can be started using one of the following
 
 For more information, see the `Stack commissioning start sequence`_ section in the ZBOSS stack documentation.
 
-In the |NCS|, the application can use :ref:`lib_zigbee_signal_handler` to handle the ZBOSS signals and start the commissioning.
+With the |addon|, the application can use :ref:`lib_zigbee_signal_handler` to handle the ZBOSS signals and start the commissioning.
 
 .. _zigbee_commissioning_modes:
 
@@ -41,7 +44,7 @@ Commissioning modes
 
 Zigbee commissioning is organized into four different modes:
 
-* Touchlink commissioning (optional; not supported in the |NCS|)
+* Touchlink commissioning (optional; not supported in the |addon| for the |NCS|)
 * Network Steering
 * Network Formation
 * Finding and Binding (optional)
@@ -69,7 +72,7 @@ Touchlink
 =========
 
 .. note::
-      The Touchlink mode is optional in Zigbee and is not supported in the |NCS|.
+   The Touchlink mode is optional in Zigbee and is not supported in the |addon| for the |NCS|.
 
 The Touchlink mode allows commissioning of devices in close proximity to each other, which means that the key criterium for this mode is the signal strength.
 It involves an initiator device and a target device, where the initiator is a member of an existing Zigbee network or it can form a new network.
@@ -108,10 +111,10 @@ The new device must be authenticated and authorized to become part of the networ
 For this purpose, it needs credentials, which usually take form of a network key.
 For `Centralized security network`_, the authentication and authorization also involves establishing a unique Trust Center Link Key (TCLK).
 
-Network Steering in the |NCS|
+Network Steering in the |addon| for the |NCS|
    In the ZBOSS stack, Network Steering is started using the `ZB_BDB_NETWORK_STEERING`_ bit mask.
 
-   In the |NCS|, Network Steering for a node on a network can be started using the following additional options:
+   In the |addon|, Network Steering for a node on a network can be started using the following additional options:
 
    * When running the :ref:`Zigbee Coordinator sample <zigbee_network_coordinator_sample>`, you can press the associated button.
    * If you are using the :ref:`lib_zigbee_shell` library in your application, you can use the ``bdb start`` command.
@@ -139,10 +142,10 @@ Depending on the node role:
 If Network Formation is successful, you can add nodes to the new network using `Network Steering`_.
 If unsuccessful, the commissioning procedure stops here.
 
-Network Formation in the |NCS|
+Network Formation in the |addon| for the |NCS|
    In the ZBOSS stack, Network Formation is started using the `ZB_BDB_NETWORK_FORMATION`_ bit mask.
 
-   In the |NCS|, when using the :ref:`lib_zigbee_signal_handler` and the application implements the Zigbee Coordinator role, the Network Formation procedure is started right after the stack initialization.
+   In the |addon|, when using the :ref:`lib_zigbee_signal_handler` and the application implements the Zigbee Coordinator role, the Network Formation procedure is started right after the stack initialization.
 
 Centralized security network
 ----------------------------
@@ -196,7 +199,7 @@ Depending on the device type:
 
 Finding and Binding can be terminated if there are no corresponding clusters on the target node.
 
-Finding and Binding in the |NCS|
+Finding and Binding in the |addon| for the |NCS|
    In the ZBOSS stack, Finding and Binding is started using the `ZB_BDB_FINDING_N_BINDING`_ bit mask.
 
    Apart from the BDB top-level procedure API, you can use the `zb_bdb_finding_binding_initiator()`_ function to manually control which binding table entries are to be created.

docs/conf.py

@@ -9,7 +9,7 @@
 # -- Project information -----------------------------------------------------
 # https://www.sphinx-doc.org/en/master/usage/configuration.html#project-information
 
-project = 'nRF Connect SDK - Zigbee R23 add-on'
+project = 'Zigbee R23 add-on for nRF Connect SDK'
 copyright = '2024, Nordic Semiconductor'
 author = 'Nordic Semiconductor'
 release = '1.0.0'