rename Autoware Universe

Signed-off-by: Mete Fatih Cırıt <mfc@autoware.org>

Author: xmfcx

common/README.md

@@ -2,7 +2,7 @@
 
 ## Getting Started
 
-The Autoware.Universe Common folder consists of common and testing libraries that are used by other Autoware components, as well as useful plugins for visualization in RVIZ2.
+The Autoware Universe Common folder consists of common and testing libraries that are used by other Autoware components, as well as useful plugins for visualization in RVIZ2.
 
 !!! note
 

common/autoware_cuda_dependency_meta/README.md

@@ -2,4 +2,4 @@
 
 ## Purpose
 
-This is a virtual package that packages on Autoware.universe that use CUDA must depend on.
+This is a virtual package that packages on Autoware Universe that use CUDA must depend on.

planning/README.md

@@ -2,11 +2,11 @@
 
 ## Getting Started
 
-The Autoware.Universe Planning Modules represent a cutting-edge component within the broader open-source autonomous driving software stack. These modules play a pivotal role in autonomous vehicle navigation, skillfully handling route planning, dynamic obstacle avoidance, and real-time adaptation to varied traffic conditions.
+The Autoware Universe Planning Modules represent a cutting-edge component within the broader open-source autonomous driving software stack. These modules play a pivotal role in autonomous vehicle navigation, skillfully handling route planning, dynamic obstacle avoidance, and real-time adaptation to varied traffic conditions.
 
 - For high level concept of Planning Components, please refer to [Planning Component Design Document](https://autowarefoundation.github.io/autoware-documentation/main/design/autoware-architecture/planning/)
 - To understand how Planning Components interacts with other components, please refer to [Planning Component Interface Document](https://autowarefoundation.github.io/autoware-documentation/main/design/autoware-interfaces/components/planning/)
-- The [Node Diagram](https://autowarefoundation.github.io/autoware-documentation/main/design/autoware-architecture/node-diagram/) illustrates the interactions, inputs, and outputs of all modules in the Autoware.Universe, including planning modules.
+- The [Node Diagram](https://autowarefoundation.github.io/autoware-documentation/main/design/autoware-architecture/node-diagram/) illustrates the interactions, inputs, and outputs of all modules in the Autoware Universe, including planning modules.
 
 ## Planning Module
 

planning/autoware_mission_planner_universe/README.md

@@ -8,7 +8,7 @@ Dynamic objects (e.g. pedestrians and other vehicles) and dynamic map informatio
 Therefore, the output topic is only published when the goal pose or check points are given and will be latched until the new goal pose or check points are given.
 
 The core implementation does not depend on a map format. Any planning algorithms can be added as plugin modules.
-In current Autoware.universe, only the plugin for Lanelet2 map format is supported.
+In current Autoware Universe, only the plugin for Lanelet2 map format is supported.
 
 This package also manages routes for MRM. The `route_selector` node duplicates the `mission_planner` interface and provides it for normal and MRM respectively.
 It distributes route requests and planning results according to current MRM operation state.

simulator/autoware_carla_interface/README.md

@@ -1,6 +1,6 @@
 # autoware_carla_interface
 
-## ROS 2/Autoware.universe bridge for CARLA simulator
+## ROS 2 / Autoware Universe bridge for CARLA simulator
 
 Thanks to <https://github.com/gezp> for ROS 2 Humble support for CARLA Communication.
 This ros package enables communication between Autoware and CARLA for autonomous driving simulation.