Apply suggestions from code review

Co-authored-by: Karl Söderby <35461661+karlsoderby@users.noreply.github.com>

Author: Federico

content/software/ide-v1/tutorials/ide-v1-security/ide-v1-security.md

@@ -1,6 +1,7 @@
 ---
 title: 'Security of Arduino IDE'
-description: 'Learn the secure development process behind Arduino IDE.'
+description: 'Learn about the secure development process behind the Arduino IDE.'
+
 tags:
  - Security
 author: 'Arduino Security Team'
@@ -10,7 +11,8 @@ Arduino IDE 2.x is the latest version of the Arduino Programming tool and it is
 
 Arduino is committed to regularly monitor and update security measures applied to the Arduino IDE to ensure proper protection from any threats or vulnerabilities detected.
 
-Arduino defined principles and requirements to be followed within the secure development lifecycle of Hardware, System and Software and the development of the open-source Arduino software makes no exception. In particular, Arduino follows the **Secure by Design** principle in every stage of the software development and the **Security Principles** listed below are followed during the secure development lifecycle:
+Arduino's defined principles and requirements to be followed within the secure development lifecycle of Hardware, System and Software and the development of the open-source Arduino software makes no exception. In particular, Arduino follows the **Secure by Design** principle in every stage of the software development and the **Security Principles** listed below are followed during the secure development lifecycle:
+
 
 - **Apply Defense in Depth**: Layered security mechanisms are in place to increase security as a whole.
 - **Use a Positive Security Model**: A ‘positive’ security model defines what is allowed and rejects everything else.
@@ -38,15 +40,17 @@ As part of the security testing activities, Arduino periodically performs the fo
 
 Finally, should an Arduino user or customer suspect a vulnerability or security issue, they are invited to report it as described in our Coordinated Vulnerability Disclosure policy available at: [https://www.arduino.cc/en/security](https://www.arduino.cc/en/security).
 
-## Third party components
+## Third Party Components
+
 In the process of conducting Secure Component Analysis, Arduino puts particular attention on the aforementioned external dependencies (Eclipse Theia and OpenJS Electron) and reports any found vulnerability to the respective project maintainer:
 
 - Eclipse Theia manages vulnerabilities using the process described in [https://www.eclipse.org/security](https://www.eclipse.org/security).
 - OpenJS Electron vulnerabilities are managed using the process described in [https://www.electronjs.org/docs/latest/tutorial/security](https://www.electronjs.org/docs/latest/tutorial/security).
 
 When vulnerabilities in third party components are fixed by the respective maintainer, Arduino will update the component involved as required, in a commercially reasonable time, based on the severity of the identified vulnerability.
 
-## Versions management
+## Version Management
+
 When it comes to managing multiple versions of the Arduino IDE, the following policy will be applied:
 
 - all security principles that are applicable to the process (design, development, testing, release) will apply to any version currently in development

content/software/ide-v2/tutorials/ide-v2-security/ide-v2-security.md

@@ -10,7 +10,8 @@ Arduino IDE 2.x is the latest version of the Arduino Programming tool and it is
 
 Arduino is committed to regularly monitor and update security measures applied to the Arduino IDE to ensure proper protection from any threats or vulnerabilities detected.
 
-Arduino defined principles and requirements to be followed within the secure development lifecycle of Hardware, System and Software and the development of the open-source Arduino software makes no exception. In particular, Arduino follows the **Secure by Design** principle in every stage of the software development and the **Security Principles** listed below are followed during the secure development lifecycle:
+Arduino's defined principles and requirements to be followed within the secure development lifecycle of Hardware, System and Software and the development of the open-source Arduino software makes no exception. In particular, Arduino follows the **Secure by Design** principle in every stage of the software development and the **Security Principles** listed below are followed during the secure development lifecycle:
+
 
 - **Apply Defense in Depth**: Layered security mechanisms are in place to increase security as a whole.
 - **Use a Positive Security Model**: A ‘positive’ security model defines what is allowed and rejects everything else.
@@ -38,15 +39,17 @@ As part of the security testing activities, Arduino periodically performs the fo
 
 Finally, should an Arduino user or customer suspect a vulnerability or security issue, they are invited to report it as described in our Coordinated Vulnerability Disclosure policy available at: [https://www.arduino.cc/en/security](https://www.arduino.cc/en/security).
 
-## Third party components
+## Third Party Components
+
 In the process of conducting Secure Component Analysis, Arduino puts particular attention on the aforementioned external dependencies (Eclipse Theia and OpenJS Electron) and reports any found vulnerability to the respective project maintainer:
 
 - Eclipse Theia manages vulnerabilities using the process described in [https://www.eclipse.org/security](https://www.eclipse.org/security).
 - OpenJS Electron vulnerabilities are managed using the process described in [https://www.electronjs.org/docs/latest/tutorial/security](https://www.electronjs.org/docs/latest/tutorial/security).
 
 When vulnerabilities in third party components are fixed by the respective maintainer, Arduino will update the component involved as required, in a commercially reasonable time, based on the severity of the identified vulnerability.
 
-## Versions management
+## Version Management
+
 When it comes to managing multiple versions of the Arduino IDE, the following policy will be applied:
 
 - all security principles that are applicable to the process (design, development, testing, release) will apply to any version currently in development