Upgrade to the new SDoc syntax: [SECTION] -> [[SECTION]]

As of the version 0.9.1, StrictDoc has switched to a new syntax for
defining SECTIONs. From now on, all sections must be defined as

`[[SECTION]]` instead of `[SECTION]`.

The rationale for the migration is explained in the related GitHub
ticket:

[Migration: SDoc model: Merge Section, Node, Composite Node into just
Node #2193](strictdoc-project/strictdoc#2193)

**IMPORTANT:** When this PR is reviewed and merged, all existing PRs
should be updated to only have [[SECTION]] tags instead of [SECTION].

See also the migration guide for further reference:

https://strictdoc.readthedocs.io/en/stable/stable/docs/strictdoc_01_user_guide.html#SECTION-UG-NODE-MIGRATION

**StrictDoc 0.9.1 version is needed for this changeset to work.**

Signed-off-by: Stanislav Pankevich [email protected]

Author: stanislaw

docs/software_requirements/software_requirements.sgra

@@ -1,5 +1,15 @@
 [GRAMMAR]
 ELEMENTS:
+- TAG: SECTION
+  PROPERTIES:
+    IS_COMPOSITE: True
+  FIELDS:
+  - TITLE: UID
+    TYPE: String
+    REQUIRED: False
+  - TITLE: TITLE
+    TYPE: String
+    REQUIRED: True
 - TAG: REQUIREMENT
   FIELDS:
   - TITLE: UID

docs/software_requirements/thread_scheduling.sdoc

@@ -10,7 +10,7 @@ STATEMENT: >>>
 SPDX-License-Identifier: Apache-2.0
 <<<
 
-[SECTION]
+[[SECTION]]
 TITLE: Thread Scheduling
 
 [REQUIREMENT]
@@ -49,9 +49,9 @@ USER_STORY: >>>
 As a Zephyr RTOS user I want Zephyr OS to provide synchronization mechanisms between the CPU cores and the access to common resources.
 <<<
 
-[/SECTION]
+[[/SECTION]]
 
-[SECTION]
+[[SECTION]]
 TITLE: Thread Scheduling
 
 [REQUIREMENT]
@@ -161,4 +161,4 @@ USER_STORY: >>>
 As a Zephyr RTOS user, I want to be able to configure my RTOS in the way, that the CPU resources are shared evenly among executed threads of the same priority.
 <<<
 
-[/SECTION]
+[[/SECTION]]

docs/system_requirements/index.sdoc

@@ -165,7 +165,7 @@ USER_STORY: >>>
 As a Zephyr RTOS user I want to be able to control the power mode of the MCU and its peripherals to take advantage of the hardware features and to be able to implement low power or battery driven long life applications.
 <<<
 
-[SECTION]
+[[SECTION]]
 TITLE: Multi core and SMP
 
 [REQUIREMENT]
@@ -194,9 +194,9 @@ USER_STORY: >>>
 As a Zephyr RTOS user, I want to be able to control which thread will run on which CPU.
 <<<
 
-[/SECTION]
+[[/SECTION]]
 
-[SECTION]
+[[SECTION]]
 TITLE: Thread Synchronization
 
 [REQUIREMENT]
@@ -222,9 +222,9 @@ STATEMENT: >>>
 The system shall implement a semaphore synchronization primitive for coordinating access to shared resources among multiple threads.
 <<<
 
-[/SECTION]
+[[/SECTION]]
 
-[SECTION]
+[[SECTION]]
 TITLE: Threads
 
 [REQUIREMENT]
@@ -266,7 +266,7 @@ USER_STORY: >>>
 As a Zephyr RTOS user, I want to be able to give my threads different priorities for execution.
 <<<
 
-[/SECTION]
+[[/SECTION]]
 
 [REQUIREMENT]
 UID: ZEP-SYRS-18
@@ -294,7 +294,7 @@ USER_STORY: >>>
 As a Zephyr RTOS user, I want to be able to trace different OS operations.
 <<<
 
-[SECTION]
+[[SECTION]]
 TITLE: Condition Variables
 
 [REQUIREMENT]
@@ -307,9 +307,9 @@ STATEMENT: >>>
 The Zephyr RTOS shall provide a framework to synchronize threads based on a condition variable.
 <<<
 
-[/SECTION]
+[[/SECTION]]
 
-[SECTION]
+[[SECTION]]
 TITLE: Queues
 
 [REQUIREMENT]
@@ -322,4 +322,4 @@ STATEMENT: >>>
 The Zephyr RTOS shall implement a queue which can be used to pass data between threads and interrupt service routines.
 <<<
 
-[/SECTION]
+[[/SECTION]]

docs/system_requirements/system_requirements.sgra

@@ -1,5 +1,15 @@
 [GRAMMAR]
 ELEMENTS:
+- TAG: SECTION
+  PROPERTIES:
+    IS_COMPOSITE: True
+  FIELDS:
+  - TITLE: UID
+    TYPE: String
+    REQUIRED: False
+  - TITLE: TITLE
+    TYPE: String
+    REQUIRED: True
 - TAG: REQUIREMENT
   FIELDS:
   - TITLE: UID

requirements.txt

@@ -1 +1,2 @@
-strictdoc
+strictdoc>=0.9.1
+