From e4be3d8961f6edc08958111523062600a31b629a Mon Sep 17 00:00:00 2001 From: EyalBrilling <43183029+EyalBrilling@users.noreply.github.com> Date: Mon, 11 Dec 2023 21:04:36 +0200 Subject: [PATCH] Fix links to README. (#417) ros_ign_bridge isn't a valid folder,ros_gz_bridge is. --- citadel/ros2_integration.md | 4 ++-- dome/ros2_integration.md | 4 ++-- edifice/ros2_integration.md | 4 ++-- fortress/ros2_integration.md | 4 ++-- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/citadel/ros2_integration.md b/citadel/ros2_integration.md index 8a0010e48..917c6892f 100644 --- a/citadel/ros2_integration.md +++ b/citadel/ros2_integration.md @@ -6,7 +6,7 @@ from ROS and apply it to Ignition and vice versa. ## ros_ign_bridge -`ros_ign_bridge` provides a network bridge which enables the exchange of messages between ROS 2 and Ignition Transport. Its support is limited to only certain message types. Please, check this [README](https://github.com/ignitionrobotics/ros_ign/blob/ros2/ros_ign_bridge/README.md) to verify if your message type is supported by the bridge. +`ros_ign_bridge` provides a network bridge which enables the exchange of messages between ROS 2 and Ignition Transport. Its support is limited to only certain message types. Please, check this [README](https://github.com/ignitionrobotics/ros_ign/blob/ros2/ros_gz_bridge/README.md) to verify if your message type is supported by the bridge. ## Requirements @@ -32,7 +32,7 @@ The ROS message type is followed by an `@`, `[`, or `]` symbol where: * `[` is a bridge from Ignition to ROS. * `]` is a bridge from ROS to Ignition. -Have a look at these [examples](https://github.com/ignitionrobotics/ros_ign/blob/ros2/ros_ign_bridge/README.md#example-1a-ignition-transport-talker-and-ros-2-listener) +Have a look at these [examples](https://github.com/ignitionrobotics/ros_ign/blob/ros2/ros_gz_bridge/README.md#example-1a-ignition-transport-talker-and-ros-2-listener) explaining how to make communication connections from ROS to Ignition and vice versa. ## Publish key strokes to ROS diff --git a/dome/ros2_integration.md b/dome/ros2_integration.md index 1643603b1..de29164cb 100644 --- a/dome/ros2_integration.md +++ b/dome/ros2_integration.md @@ -6,7 +6,7 @@ from ROS and apply it to Ignition and vice versa. ## ros_ign_bridge -`ros_ign_bridge` provides a network bridge which enables the exchange of messages between ROS 2 and Ignition Transport. Its support is limited to only certain message types. Please, check this [README](https://github.com/ignitionrobotics/ros_ign/blob/ros2/ros_ign_bridge/README.md) to verify if your message type is supported by the bridge. +`ros_ign_bridge` provides a network bridge which enables the exchange of messages between ROS 2 and Ignition Transport. Its support is limited to only certain message types. Please, check this [README](https://github.com/ignitionrobotics/ros_ign/blob/ros2/ros_gz_bridge/README.md) to verify if your message type is supported by the bridge. ## Requirements @@ -34,7 +34,7 @@ The ROS message type is followed by an `@`, `[`, or `]` symbol where: * `[` is a bridge from Ignition to ROS. * `]` is a bridge from ROS to Ignition. -Have a look at these [examples](https://github.com/ignitionrobotics/ros_ign/blob/ros2/ros_ign_bridge/README.md#example-1a-ignition-transport-talker-and-ros-2-listener) +Have a look at these [examples](https://github.com/ignitionrobotics/ros_ign/blob/ros2/ros_gz_bridge/README.md#example-1a-ignition-transport-talker-and-ros-2-listener) explaining how to make communication connections from ROS to Ignition and vice versa. ## Publish key strokes to ROS diff --git a/edifice/ros2_integration.md b/edifice/ros2_integration.md index 0e49381e5..d290355ac 100644 --- a/edifice/ros2_integration.md +++ b/edifice/ros2_integration.md @@ -6,7 +6,7 @@ from ROS and apply it to Ignition and vice versa. ## ros_ign_bridge -`ros_ign_bridge` provides a network bridge which enables the exchange of messages between ROS 2 and Ignition Transport. Its support is limited to only certain message types. Please, check this [README](https://github.com/ignitionrobotics/ros_ign/blob/ros2/ros_ign_bridge/README.md) to verify if your message type is supported by the bridge. +`ros_ign_bridge` provides a network bridge which enables the exchange of messages between ROS 2 and Ignition Transport. Its support is limited to only certain message types. Please, check this [README](https://github.com/ignitionrobotics/ros_ign/blob/ros2/ros_gz_bridge/README.md) to verify if your message type is supported by the bridge. ## Requirements @@ -34,7 +34,7 @@ The ROS message type is followed by an `@`, `[`, or `]` symbol where: * `[` is a bridge from Ignition to ROS. * `]` is a bridge from ROS to Ignition. -Have a look at these [examples](https://github.com/ignitionrobotics/ros_ign/blob/ros2/ros_ign_bridge/README.md#example-1a-ignition-transport-talker-and-ros-2-listener) +Have a look at these [examples](https://github.com/ignitionrobotics/ros_ign/blob/ros2/ros_gz_bridge/README.md#example-1a-ignition-transport-talker-and-ros-2-listener) explaining how to make communication connections from ROS to Ignition and vice versa. ## Publish key strokes to ROS diff --git a/fortress/ros2_integration.md b/fortress/ros2_integration.md index daa3704ac..a5e5090f8 100644 --- a/fortress/ros2_integration.md +++ b/fortress/ros2_integration.md @@ -6,7 +6,7 @@ from ROS and apply it to Ignition and vice versa. ## ros_ign_bridge -`ros_ign_bridge` provides a network bridge which enables the exchange of messages between ROS 2 and Ignition Transport. Its support is limited to only certain message types. Please, check this [README](https://github.com/ignitionrobotics/ros_ign/blob/ros2/ros_ign_bridge/README.md) to verify if your message type is supported by the bridge. +`ros_ign_bridge` provides a network bridge which enables the exchange of messages between ROS 2 and Ignition Transport. Its support is limited to only certain message types. Please, check this [README](https://github.com/ignitionrobotics/ros_ign/blob/ros2/ros_gz_bridge/README.md) to verify if your message type is supported by the bridge. ## Requirements @@ -32,7 +32,7 @@ The ROS message type is followed by an `@`, `[`, or `]` symbol where: * `[` is a bridge from Ignition to ROS. * `]` is a bridge from ROS to Ignition. -Have a look at these [examples](https://github.com/ignitionrobotics/ros_ign/blob/ros2/ros_ign_bridge/README.md#example-1a-ignition-transport-talker-and-ros-2-listener) +Have a look at these [examples](https://github.com/ignitionrobotics/ros_ign/blob/ros2/ros_gz_bridge/README.md#example-1a-ignition-transport-talker-and-ros-2-listener) explaining how to make communication connections from ROS to Ignition and vice versa. ## Publish key strokes to ROS