From 994b95c046dcb9198fd4895644717fb8174cb055 Mon Sep 17 00:00:00 2001 From: Darius Maitia Date: Mon, 16 Oct 2023 17:04:33 +0200 Subject: [PATCH] Fix typo --- content/blog/2023-10-03-zenoh-dragonite.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/2023-10-03-zenoh-dragonite.md b/content/blog/2023-10-03-zenoh-dragonite.md index 6ce9e1f2..1438e665 100644 --- a/content/blog/2023-10-03-zenoh-dragonite.md +++ b/content/blog/2023-10-03-zenoh-dragonite.md @@ -152,7 +152,7 @@ Another significant change is the new fine-grained bridging mode config. Now use As a result, the bridge is capable to expose ROS1 topics for publishers, subscribers, services and clients into Zenoh network as a set of Zenoh publishers, subscribers, queryables and queries, providing ROS1 system all set of Zenoh features, like highly-efficient and flexible network operation, storage-based data caching, etc. Moreover, multiple ROS1 systems bridged into one Zenoh network are capable of seeing each other and interact seamlessly. -ROS1 to Zenog Bridge aims to be completely transparent, making interaction with remote ROS1 topics as if they were local. The integration to any existing ROS1 system does not require its tuning, recompilation etc (of course, if its application logic won't get mad of seeing remote ROS1 topics in its environment :) ). +ROS1 to Zenoh Bridge aims to be completely transparent, making interaction with remote ROS1 topics as if they were local. The integration to any existing ROS1 system does not require its tuning, recompilation etc (of course, if its application logic won't get mad of seeing remote ROS1 topics in its environment :) ). To test a new bridge, please try the following: