maksimdrachov · maarten1C96 · Apr 2, 2024 · Apr 2, 2024 · Apr 3, 2024 · Apr 3, 2024
diff --git a/.DS_Store b/.DS_Store
diff --git a/.gitignore b/.gitignore
@@ -56,4 +56,8 @@ tags
 
 _site
 .jekyll-cache
-vendor
+vendor
+
+**/.DS_Store
+.vscode/
+.history/
diff --git a/_config.yml b/_config.yml
@@ -1,6 +1,8 @@
 title: Zephyr Tutorial
 remote_theme: bedroesb/just-the-docs
 
+# baseurl: "/zephyr-rtos-tutorial"
+
 plugins:
   - jekyll-relative-links
   - jekyll-remote-theme

diff --git a/docs/.DS_Store b/docs/.DS_Store
diff --git a/docs/1-zephyr-setup/install/mac-os.md b/docs/1-zephyr-setup/install/mac-os.md
@@ -119,5 +119,5 @@ A successful flash looks like this:
 
 {: .warning}
 > Some boards will require installing an additional `pyocd` package! 
-> ![pyocd-error](../../../images/zephyr-setup/pyocd-error.png)
+> ![pyocd-error](/../images/zephyr-setup/pyocd-error.png)
 > For Nucleo L552ZE-Q: `pyocd pack install stm32l552zetxq` (see [pyocd/target_support](https://pyocd.io/docs/target_support.html#managed-packs))
diff --git a/docs/1-zephyr-setup/setup/mac-os.md b/docs/1-zephyr-setup/setup/mac-os.md
@@ -60,6 +60,7 @@ west flash
 
 {: .note }
 > If you've previously made a build for a different board, remove the old build first: `rm -rf build`
+> For convenience, full path to the basic-sample page: `cd ~/zephyrproject/zephyr-rtos-tutorial/exercises/basic-sample`
 
 - Verify the serial output:
 

diff --git a/docs/2-introduction/rtos-basics.md b/docs/2-introduction/rtos-basics.md
@@ -28,4 +28,4 @@ Each **thread** (or task) will use registers and memory as it executes. The whol
 
 Along with threads, you'll be using primitives such as **queues**, **mutexes** and **semaphores** for inter-thread communication. Then each RTOS provides varying levels of support for different protocols such as **TCP/IP**, **Bluetooth**, **LoRaWan**,... This makes your life easier, since now you don't need to study these protocols as in-depth. You'll get a series of API calls which should increase speed of development.
 
-![rtos-basic-execution](../../images/2-introduction/rtos_basic_execution.gif)
+![rtos-basic-execution](/images/2-introduction/rtos_basic_execution.gif)
diff --git a/docs/_includes/incomplete.md b/docs/_includes/incomplete.md
@@ -0,0 +1,2 @@
+{: .warning}
+This section is incomplete. You can help by [contributing](https://github.com/maksimdrachov/zephyr-rtos-tutorial).
diff --git a/exercises/basic-sample/src/main.c b/exercises/basic-sample/src/main.c
@@ -4,7 +4,7 @@
  * SPDX-License-Identifier: Apache-2.0
  */
 
-#include <zephyr/zephyr.h>
+#include <zephyr/kernel.h>
 #include <zephyr/device.h>
 #include <zephyr/devicetree.h>
 

diff --git a/images/.DS_Store b/images/.DS_Store
Original file line number	Diff line number	Diff line change
Expand Up		@@ -28,4 +28,4 @@ Each thread (or task) will use registers and memory as it executes. The whol

		Along with threads, you'll be using primitives such as queues, mutexes and semaphores for inter-thread communication. Then each RTOS provides varying levels of support for different protocols such as TCP/IP, Bluetooth, LoRaWan,... This makes your life easier, since now you don't need to study these protocols as in-depth. You'll get a series of API calls which should increase speed of development.

		![rtos-basic-execution](../../images/2-introduction/rtos_basic_execution.gif)
		![rtos-basic-execution](/images/2-introduction/rtos_basic_execution.gif)
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,2 @@
		{: .warning}
		This section is incomplete. You can help by [contributing](https://github.com/maksimdrachov/zephyr-rtos-tutorial).