Merge to production

content/learning-paths/embedded-systems/yocto_qemu/yocto_build.md

@@ -10,14 +10,14 @@ layout: "learningpathall"
 
 ## Before you begin
 
-The [Yocto Project](https://www.yoctoproject.org/) is an open-source project with a build system that allows software developers create custom embedded Linux OS distributions regardless of the hardware architecture. 
+The [Yocto Project](https://www.yoctoproject.org/) is an open-source project with a build system that allows software developers to create custom embedded Linux OS distributions regardless of the hardware architecture. 
 Developers can configure their custom builds of Yocto using a set of recipes. In this Learning Path you will learn the steps to build a minimal Yocto Linux image for a 64-bit Arm target and run it on [QEMU](https://www.qemu.org/). 
 
 ## Build minimal Yocto Linux image for 64-bit Arm target
 
-Poky is a reference distribution of the Yocto Project. It is a great starting point to build your own custom distribution as it contains both the build system and the the baseline functional distribution. Along with containing recipes for real target boards, it also contains the recipes for building the image for example 64-bit Arm machines supported in QEMU. The example 64-bit machine emulated by QEMU does not emulate any particular board but is a great starting point to learn and try the basics of running this distribution.
+Poky is a reference distribution of the Yocto Project. It is a great starting point to build your own custom distribution as it contains both the build system and the the baseline functional distribution. Along with containing recipes for real target boards, it also contains the recipes for building the image, for example 64-bit Arm machines supported in QEMU. The example 64-bit machine emulated by QEMU does not emulate any particular board but is a great starting point to learn and try the basics of running this distribution.
 
-The first step is to install the packages required to build and run Yocto
+The first step is to install the packages required to build and run Yocto:
 
 ```bash
 sudo apt update
@@ -30,7 +30,7 @@ git clone git://git.yoctoproject.org/poky
 cd poky
 git checkout tags/yocto-4.0.6 -b yocto-4.0.6-local
 ```
-Next source the script as shown below to initialize your build environment for your 64-bit Arm example machine QEMU target
+Next source the script as shown below to initialize your build environment for your 64-bit Arm example machine QEMU target:
 
 ```bash
 source oe-init-build-env build-qemu-arm64

content/learning-paths/laptops-and-desktops/win_aws_iot/_index.md

@@ -0,0 +1,35 @@
+---
+title: Create IoT applications with Windows on Arm and AWS IoT Core
+
+minutes_to_complete: 120
+
+who_is_this_for: This learning path is for developers who want to learn how to create IoT applications using Windows on Arm and AWS IoT Core.
+
+learning_objectives:
+    - Create a Node.js that streams synthesized sensor data to AWS cloud.
+    - Register a device in AWS IoT Core.    
+    - Send data from a device to AWS IoT Core.
+
+prerequisites:
+    - A Windows-on-Arm computer such as [Windows Dev Kit 2023](https://learn.microsoft.com/en-us/windows/arm/dev-kit), Lenovo Thinkpad X13s running Windows 11, or a Windows-on-Arm [virtual machine](/learning-paths/cross-platform/woa_azure/).
+    - Any code editor. We recommend using Visual Studio Code.
+
+author_primary: Dawid Borycki
+
+### Tags
+skilllevels: Advanced
+subjects: Migration to Arm
+armips:
+    - Cortex-A
+operatingsystems:
+    - Windows
+tools_software_languages:
+    - Node.js    
+    - Visual Studio
+
+### FIXED, DO NOT MODIFY
+# ================================================================================
+weight: 1                       # _index.md always has weight of 1 to order correctly
+layout: "learningpathall"       # All files under learning paths have this same wrapper
+learning_path_main_page: "yes"  # This should be surfaced when looking for related content. Only set for _index.md of learning path content.
+---

content/learning-paths/laptops-and-desktops/win_aws_iot/_next-steps.md

@@ -0,0 +1,35 @@
+---
+# ================================================================================
+#       Edit
+# ================================================================================
+
+next_step_guidance: >
+   You have now learned how to create IoT applications with Windows on Arm and AWS IoT Core. You might be interested in learning how to use web technologies for creating cross-platform desktop apps.
+# 1-3 sentence recommendation outlining how the reader can generally keep learning about these topics, and a specific explanation of why the next step is being recommended.
+
+recommended_path: "/learning-paths/laptops-and-desktops/electron"
+# Link to the next learning path being recommended(For example this could be /learning-paths/servers-and-cloud-computing/mongodb).
+
+
+# further_reading links to references related to this path. Can be:
+    # Manuals for a tool / software mentioned   (type: documentation)
+    # Blog about related topics                 (type: blog)
+    # General online references                 (type: website) 
+
+further_reading:
+    - resource:
+        title: AWS IoT Core Developer Guide
+        link: https://docs.aws.amazon.com/iot/latest/developerguide
+        type: documentation
+    - resource:
+        title: Connecting a device to AWS IoT Core by using the AWS IoT Device SDK
+        link: https://docs.aws.amazon.com/iot/latest/developerguide/sdk-tutorials.html
+        type: documentation
+
+# ================================================================================
+#       FIXED, DO NOT MODIFY
+# ================================================================================
+weight: 21                  # set to always be larger than the content in this path, and one more than 'review'
+title: "Next Steps"         # Always the same
+layout: "learningpathall"   # All files under learning paths have this same wrapper
+---

content/learning-paths/laptops-and-desktops/win_aws_iot/_review.md

@@ -0,0 +1,52 @@
+---
+# ================================================================================
+#       Edit
+# ================================================================================
+
+# Always 3 questions. Should try to test the reader's knowledge, and reinforce the key points you want them to remember.
+    # question:         A one sentence question
+    # answers:          The correct answers (from 2-4 answer options only). Should be surrounded by quotes.
+    # correct_answer:   An integer indicating what answer is correct (index starts from 0)
+    # explanation:      A short (1-3 sentence) explanation of why the correct answer is correct. Can add additional context if desired
+
+
+review:
+    - questions:
+        question: >
+            Does AWS IoT Core use MQTT protocol?
+        answers:
+            - "No"
+            - "Yes"
+        correct_answer: 2
+        explanation: >
+            Yes, AWS IoT Core uses MQTT protocol for secure data transmission.
+
+    - questions:
+        question: >
+            Can you use the device's certificate to manage device permissions in AWS IoT Core?
+        answers:
+            - "Yes"
+            - "No"            
+        correct_answer: 1
+        explanation: >
+            Yes, you attach the policy to the certificate in order to control device permissions.
+
+    - questions:
+        question: >
+            What do you use to connect a device to the AWS IoT Core?
+        answers:
+            - "AWS Device SDK"
+            - "AWS IoT Core SDK"
+            - "AWS Core SDK"
+        correct_answer: 1
+        explanation: > 
+            You use AWS Device SDK to implement applications that connect to the AWS cloud.
+
+
+# ================================================================================
+#       FIXED, DO NOT MODIFY
+# ================================================================================
+title: "Review"                 # Always the same title
+weight: 20                      # Set to always be larger than the content in this path
+layout: "learningpathall"       # All files under learning paths have this same wrapper
+---