Update wiki/interfacing/ros1_ros2_bridge.md

Co-authored-by: Nevin Valsaraj <5763537+nevalsar@users.noreply.github.com>

Author: vib2810

wiki/interfacing/ros1_ros2_bridge.md

@@ -13,7 +13,7 @@ ROS 2 is widely used nowadays due to its better security features and code organ
 
 ## Conceptual Overview
 ### ROS 1 - ROS 2 Bridge
-The [ROS 1 bridge](https://github.com/ros2/ros1_bridge) is a ros2 package that provides nodes to bridge topics between ros 1 and ros 2. A point to be noted here is that bridging is only available on Ubuntu 20.04, as this distribution is the only one that supports both ROS 1 Noetic and ROS 2 Foxy. This package is capable of bridging the stantard ROS interfaces (messages/services) listed in the [ros2/common_interfaces](https://github.com/ros2/common_interfaces) repository. To use the bridge with custom message types, the package needs to be build from source, and the custom types should also be sourced in seperate ROS 1 and ROS 2 workspaces. Services need to be bridged explicitly between ROS 2 and ROS 1, and ROS 1 and ROS 2. 
+The [ROS 1 bridge](https://github.com/ros2/ros1_bridge) is a ros2 package that provides nodes to bridge topics between ROS 1 and ROS 2. A point to be noted here is that bridging is only available on Ubuntu 20.04, as this distribution is the only one that supports both ROS 1 Noetic and ROS 2 Foxy. This package is capable of bridging the stantard ROS interfaces (messages/services) listed in the [ros2/common_interfaces](https://github.com/ros2/common_interfaces) repository. To use the bridge with custom message types, the package needs to be build from source, and the custom types should also be sourced in seperate ROS 1 and ROS 2 workspaces. Services need to be bridged explicitly between ROS 2 and ROS 1, and ROS 1 and ROS 2. 
 
 
 ### Installation: