Skip to content

Commit f4a2eba

Browse files
committed
Address changes
1 parent 5c2337b commit f4a2eba

2 files changed

Lines changed: 3 additions & 3 deletions

File tree

_docs/overview/hardware/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,11 +30,11 @@ permalink: /docs/overview/hardware/
3030

3131
Micro-ROS aims to **bring ROS 2 to a wide set of microcontrollers** to allow having first-class ROS 2 entities in the embedded world.
3232

33-
The main targets of micro-ROS are mid-range 32-bits microcontroller families. Usually, the minimum requirements for running micro-ROS in an embedded platform are memory constrains. Since memory usage in micro-ROS is a complex matter we provide a [complete article](https://micro-ros.github.io/docs/concepts/memo_prof/) describing it and a tutorial on [how to tune the memory consuption](https://micro-ros.github.io/docs/tutorials/core/microxrcedds_rmw_configuration/) in the micro-ROS middleware.
33+
The main targets of micro-ROS are mid-range 32-bits microcontroller families. Usually, the minimum requirements for running micro-ROS in an embedded platform are memory constraints. Since memory usage in micro-ROS is a complex matter we provide a [complete article](https://micro-ros.github.io/docs/concepts/memo_prof/) describing it and a tutorial on [how to tune the memory consuption](https://micro-ros.github.io/docs/tutorials/core/microxrcedds_rmw_configuration/) in the micro-ROS middleware.
3434

3535
In general micro-ROS will need MCUs that have tens of kilobytes of RAM memory and communication peripherals that enable the micro-ROS [Client to Agent communication](https://micro-ros.github.io//docs/overview/features/).
3636

37-
The micro-ROS hardware support is divided in three categories:
37+
The micro-ROS hardware support is divided into three categories:
3838
- reference micro-ROS board,
3939
- tier 2 boards and,
4040
- community supported boards.

_posts/2020-10-01-zephyr_partnership.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ micro-ROS is now an Associate Partner of the [Zephyr Project](https://www.zephyr
77

88
<img alt="Zephyr" src="https://upload.wikimedia.org/wikipedia/commons/2/2d/Zephyr-logo.png" width="45%"/>
99

10-
Zephyr is a scalable open source Real-Time Operating System (RTOS) designed to fit resource constrained and embedded systems, with safety and security in mind. It forms part of [the Linux Foundation](https://www.linuxfoundation.org/), which supports a wide range of open source projects. Zephyr targets the same range of systems and applications with deterministic and time-critical constrains as micro-ROS, such as connected sensors and actuators, microcontrollers and small IoT devices of all kinds. micro-ROS and Zephyr complement each other by allowing to easily create heterogeneous distributed robotic systems and also integrate these devices seamlessly into the ROS 2 ecosystem.
10+
Zephyr is a scalable open source Real-Time Operating System (RTOS) designed to fit resource constrained and embedded systems, with safety and security in mind. It forms part of [the Linux Foundation](https://www.linuxfoundation.org/), which supports a wide range of open source projects. Zephyr targets the same range of systems and applications with deterministic and time-critical constraints as micro-ROS, such as connected sensors and actuators, microcontrollers and small IoT devices of all kinds. micro-ROS and Zephyr complement each other by allowing to easily create heterogeneous distributed robotic systems and also integrate these devices seamlessly into the ROS 2 ecosystem.
1111

1212
For additional information and the official press release by the Zephyr Project, follow this [link](https://www.zephyrproject.org/google-and-facebook-select-zephyr-rtos-for-next-generation-products/).
1313

0 commit comments

Comments
 (0)