doc: update for VSC extension release

Updated documentation for the changes in the VSC extension NCS 3.0.0
release. VSC-2894.

Signed-off-by: Grzegorz Ferenc <[email protected]>

Author: greg-fer

doc/nrf/app_dev/config_and_build/building.rst

@@ -20,9 +20,9 @@ Just as for creating the application, you can build the application using either
       For instructions, see `How to build an application`_ in the extension documentation.
 
       By default, the extension runs both stages of the CMake build (:ref:`configuration phase and building phase <app_build_system>`).
-      If you want to only set up the build configuration without building it, make sure the :guilabel:`Build after generating configuration` is not selected.
+      If you want to only set up the build configuration without building the final binary, make sure the :guilabel:`Generate only` checkbox is selected.
 
-      To build with :ref:`configuration_system_overview_sysbuild`, :ref:`keep the default setting selected <sysbuild_enabled_ncs>` or select the :guilabel:`Use sysbuild` radio button.
+      To build with :ref:`configuration_system_overview_sysbuild`, either :ref:`keep the default setting selected <sysbuild_enabled_ncs>` or select the :guilabel:`Use sysbuild` radio button.
 
       If you want to build with custom options or scripts, read about `Binding custom tasks to actions`_ in the extension documentation.
 

doc/nrf/app_dev/config_and_build/sysbuild/sysbuild_images.rst

@@ -9,9 +9,8 @@ Sysbuild images
 
 :ref:`configuration_system_overview_sysbuild` allows you to add additional images to your builds.
 
-
 Enabling images
-===============
+***************
 
 To add an additional image using sysbuild, you must modify the central sysbuild configuration.
 This is typically done in a `sysbuild.conf` file within an application, which is a Kconfig fragment applied to the default sysbuild configuration when a project is configured.
@@ -55,7 +54,7 @@ These options determine whether the secure boot image is included on the network
 .. _sysbuild_images_adding_custom_images:
 
 Adding custom images
-====================
+********************
 
 Custom images can be added directly to a project (or board) or to a Zephyr module, making them accessible to multiple projects.
 
@@ -99,7 +98,7 @@ This method can be used to add a new image to the existing board target.
 .. _sysbuild_images_adding_custom_network_core_images:
 
 Adding custom network core images
----------------------------------
+=================================
 
 To add an image for a different board target (like for the network core of the nRF5340 SoC), you must use a different syntax.
 This can be handled using the following approach:
@@ -162,7 +161,7 @@ This file is optional and is only needed if custom configuration needs to be set
 .. _sysbuild_images_adding_to_a_single_board:
 
 Adding to a single board
-------------------------
+========================
 
 You can place the same code as in the :ref:`sysbuild_images_adding_to_single_project` section, without the Zephyr sourcing, in a board directory.
 This enables the use of those images for any sysbuild-based project being built for that board:
@@ -193,7 +192,7 @@ sysbuild.cmake:
 .. _sysbuild_images_adding_via_a_zephyr_module:
 
 Adding through a Zephyr module
-------------------------------
+==============================
 
 To add images in a Zephyr module, create a folder within the module to hold the `Kconfig.sysbuild` and (optionally, if needed) `CMakeLists.txt` files.
 Then, add this folder to the Zephyr module file:
@@ -241,3 +240,11 @@ Kconfig.sysbuild:
     endif # !NETCORE_NONE
 
     endmenu
+
+.. _sysbuild_images_editing_in_nrfvsc:
+
+Editing sysbuild images and domains in the |nRFVSC|
+***************************************************
+
+The |nRFVSC| provides a GUI for editing sysbuild images and domains.
+See the `How to work with sysbuild domains`_ page in the extension documentation for more information.

doc/nrf/app_dev/create_application.rst

@@ -168,6 +168,7 @@ Use the following steps depending on the application placement:
 
          * :guilabel:`Create a blank application` - This will create an application with a code structure that you need to populate from scratch.
          * :guilabel:`Copy a sample` - This will create an application from an |NCS| sample or an |NCS| application.
+           If you have more than one version of the |NCS| installed, you have to choose the version from which you copy the sample or the application from.
 
       #. Enter the location and the name for the application.
          The location will be the *<west-workspace>/* directory mentioned in the :ref:`workspace application structure <create_application_types_workspace>`.

doc/nrf/includes/vsc_build_and_run_series.txt

@@ -11,6 +11,8 @@
       #. |exceptions_step|
       #. Open the nRF Connect extension in |VSC| by clicking its icon in the :guilabel:`Activity Bar`.
       #. In the extension's :guilabel:`Actions View`, click on :guilabel:`Flash`.
+         If you have more than one device connected, you will be prompted to select the device to program.
+         If the build system considers the build incomplete, using this action also triggers a rebuild before flashing.
 
       For instructions about programming with the |nRFVSC|, see `How to flash an application`_.
 

doc/nrf/installation/install_ncs.rst

@@ -207,7 +207,14 @@ For more information about the repository and development model, see the :ref:`d
       #. In the extension's :guilabel:`Welcome View`, click on :guilabel:`Manage SDKs`.
          The list of actions appears in the |VSC|'s quick pick.
       #. Click :guilabel:`Install SDK`.
-         The list of available stable SDK versions appears in the |VSC|'s quick pick.
+         The list of available stable SDK versions appears in the |VSC|'s quick pick, grouped into two categories:
+
+         * Pre-packaged SDKs - Bundled by Nordic Semiconductor.
+           Available mostly for stable releases and some preview tags.
+           Recommended for faster and more reliable download and installation.
+         * GitHub - Taken from the `nRF Connect by Nordic Semiconductor GitHub organization <nrfconnect GitHub organization_>`_.
+           Available for stable releases, but also preview tags and branches (after disabling the filter in the quick pick).
+
       #. Select the SDK version to install.
          |install_latest_version|
 

doc/nrf/installation/updating.rst

@@ -174,6 +174,9 @@ If you disabled automatic updates:
 #. The :guilabel:`Update` button appears when an update is available.
    Click the button to install the update.
 
+Sometimes the extension can offer pre-release versions.
+In such cases, you can `switch to the pre-release version of the extension`_ to test the new features before they are released.
+
 .. _west_update:
 
 Updating west from command line

doc/nrf/links.txt

@@ -945,6 +945,7 @@
 .. _`Browse samples`: https://docs.nordicsemi.com/bundle/nrf-connect-vscode/page/reference/ui_sidebar_welcome.html#browse-samples
 .. _`nRF Terminal documentation`: https://docs.nordicsemi.com/bundle/nrf-connect-vscode/page/reference/ui_panel.html#nrf-connect-and-nrf-terminal-profiles
 .. _`switch to the pre-release version of the extension`: https://docs.nordicsemi.com/bundle/nrf-connect-vscode/page/rel_notes_overview.html#switching-to-a-pre-release-version
+.. _`How to work with sysbuild domains`: https://docs.nordicsemi.com/bundle/nrf-connect-vscode/page/guides/build_multi_domain.html
 
 .. ### Source: files.nordicsemi.com