doc: bring back changelog post 1.0.0 release

Standard post-release doc updates plus fixing some
leftover comments from the release PR.

Signed-off-by: Bartosz Gentkowski <bartosz.gentkowski@nordicsemi.no>

Author: b-gent

doc/nrf-bm/app_dev/dfu/memory_partitioning.rst

@@ -133,8 +133,8 @@ The recommended sizes are based on the configuration used in |BMshort|.
 .. note::
    The sizes and configurations of slot0 and slot1 are asymmetrical.
 
-* **DK board** - Represents the partition size that you can find in the board definition files (.dts) that have been defined for the MCUboot board target in |BMshort|.
-  These sizes are not optimized but set large enough to provide enough memory to do development on multiple domains without having to adjust the partition size.
+* **DK board** - Represents the partition size that you can find in the board definition files (:file:`.dts`) that have been defined for the MCUboot board target in |BMshort|.
+  These sizes are not optimized but set large enough to provide enough memory for development on multiple domains without having to adjust the partition size.
 
 * **Development** - Represents the partition size that can be used to maximize the application space (``slot0_partition`` and ``storage_partition``) when running with default configuration of the MCUboot and firmware loader project.
   This setting does not include extra space in the ``slot1_partition`` to accommodate for updates without the risk of having to adjust the partition size.
@@ -149,7 +149,7 @@ The recommended sizes are based on the configuration used in |BMshort|.
 Optimizing your project for release
 ***********************************
 
-Reference sizes of the MCUboot and the firmware loader can be achieved using the default configuration of :ref:`ble_mcuboot_recovery_entry_sample`.
+You can achieve the reference sizes of MCUboot and firmware loader using the default configuration of the :ref:`ble_mcuboot_recovery_entry_sample` sample.
 
 For minimal size, amend the firmware loader configuration using the following Kconfig options:
 

doc/nrf-bm/doxygen/mainpage.dox

@@ -1,5 +1,5 @@
 /**
-@mainpage nRF Connect SDK Bare Metal option v1.0.0 API documentation
+@mainpage nRF Connect SDK Bare Metal option v1.0.99 API documentation
 
 <a href="topics.html">API Reference</a>
 

doc/nrf-bm/libraries/nfc/integration_notes.rst

@@ -3,8 +3,7 @@
 Integration notes
 #################
 
-When integrating the NFC libraries in your application, there are a few things to be aware of.
-See the following notes.
+When integrating the NFC libraries in your application, consider the following notes.
 
 .. contents::
    :local:

doc/nrf-bm/release_notes.rst

@@ -10,6 +10,7 @@ The following is a list of all release notes documents for various releases of t
    :caption: Subpages:
 
    release_notes/bm_software_maturity
+   release_notes/release_notes_changelog
    release_notes/release_notes_1.0.0
    release_notes/release_notes_0.9.0
    release_notes/release_notes_0.8.0

doc/nrf-bm/release_notes/release_notes_changelog.rst

@@ -1,9 +1,7 @@
-:orphan:
-
 .. _nrf_bm_release_notes_1099:
 
-Release Notes for |BMlong| v1.0.99
-##################################
+Changelog for |BMlong| v1.0.99
+##############################
 
 The most relevant changes that are present on the main branch of the nRF Connect SDK Bare Metal, as compared to the latest official release, are tracked in this file.