docs: Numerous spelling and grammer fixes in flight controller section (#26582)

docs/en/test_and_ci/integration_testing_mavsdk.md

@@ -7,7 +7,7 @@ In future we plan to generalise them for any platform/hardware.
 
 The instructions below explain how to setup and run the tests locally.
 
-:::note
+::: info
 This is the recommended integration test framework for PX4.
 :::
 

docs/en/test_and_ci/integration_testing_ros1_mavros.md

@@ -8,7 +8,7 @@ It should be used only for new test cases that _require_ ROS 1.
 [MAVSDK Integration Testing](../test_and_ci/integration_testing_mavsdk.md) is preferred when writing new tests.
 :::
 
-:::note
+::: info
 All PX4 integration tests are executed automatically by our [Continuous Integration](../test_and_ci/continous_integration.md) system.
 :::
 

docs/en/test_and_ci/unit_tests.md

@@ -133,7 +133,7 @@ The steps to create new SITL unit tests are as follows:
    }
    ```
 
-   `OPTION` can be `OPT_NOALLTEST`,`OPT_NOJIGTEST` or `0` and is considered if within px4 shell one of the two commands are called:
+   `OPTION` can be `OPT_NOALLTEST`,`OPT_NOJIGTEST` or `0` and is considered if within PX4 shell one of the two commands are called:
 
    ```sh
    pxh> tests all