fix migration tutorial titles

Signed-off-by: Mabel Zhang <[email protected]>
gazebosim · Sep 14, 2023 · bfe664b · bfe664b
1 parent 4cb5d38
commit bfe664b
Show file tree

Hide file tree

Showing 11 changed files with 11 additions and 32 deletions.
diff --git a/tutorials/migrating_ardupilot_plugin.md b/tutorials/migrating_ardupilot_plugin.md
@@ -1,6 +1,4 @@
-\page ardupilot
-
-# Case study: migrating the ArduPilot ModelPlugin from Gazebo classic to Gazebo
+\page ardupilot Case study: migrating the ArduPilot ModelPlugin from Gazebo classic to Gazebo
 
 A variety of changes are required when migrating a plugin from Gazebo classic
 to Gazebo. In this tutorial we offer as a case

diff --git a/tutorials/migration_actor_api.md b/tutorials/migration_actor_api.md
@@ -1,6 +1,4 @@
-\page migrationactorapi
-
-# Migration from Gazebo-classic: Actor API
+\page migrationactorapi Migration from Gazebo-classic: Actor API
 
 When migrating plugins from Gazebo-classic to Gazebo, developers will
 notice that the C++ APIs for both simulators are quite different. Be sure to

diff --git a/tutorials/migration_joint_api.md b/tutorials/migration_joint_api.md
@@ -1,6 +1,4 @@
-\page migrationjointapi
-
-# Migration from Gazebo-classic: Joint API
+\page migrationjointapi Migration from Gazebo-classic: Joint API
 
 When migrating plugins from Gazebo-classic to Gazebo, developers will
 notice that the C++ APIs for both simulators are quite different. Be sure to

diff --git a/tutorials/migration_light_api.md b/tutorials/migration_light_api.md
@@ -1,6 +1,4 @@
-\page migrationlightapi
-
-# Migration from Gazebo-classic: Light API
+\page migrationlightapi Migration from Gazebo-classic: Light API
 
 When migrating plugins from Gazebo-classic to Gazebo, developers will
 notice that the C++ APIs for both simulators are quite different. Be sure to

diff --git a/tutorials/migration_link_api.md b/tutorials/migration_link_api.md
@@ -1,6 +1,4 @@
-\page migrationlinkapi
-
-# Migration from Gazebo-classic: Link API
+\page migrationlinkapi Migration from Gazebo-classic: Link API
 
 When migrating plugins from Gazebo-classic to Gazebo, developers will
 notice that the C++ APIs for both simulators are quite different. Be sure to

diff --git a/tutorials/migration_model_api.md b/tutorials/migration_model_api.md
@@ -1,6 +1,4 @@
-\page migrationmodelapi
-
-# Migration from Gazebo-classic: Model API
+\page migrationmodelapi Migration from Gazebo-classic: Model API
 
 When migrating plugins from Gazebo-classic to Gazebo, developers will
 notice that the C++ APIs for both simulators are quite different. Be sure to

diff --git a/tutorials/migration_plugins.md b/tutorials/migration_plugins.md
@@ -1,6 +1,4 @@
-\page migrationplugins
-
-# Migration from Gazebo Classic: Plugins
+\page migrationplugins Migration from Gazebo Classic: Plugins
 
 Gazebo Classic supports
 [6 different C++ plugin types](http://gazebosim.org/tutorials?tut=plugins_hello_world&cat=write_plugin),

diff --git a/tutorials/migration_sdf.md b/tutorials/migration_sdf.md
@@ -1,6 +1,4 @@
-\page migrationsdf
-
-# Migration from Gazebo classic: SDF
+\page migrationsdf Migration from Gazebo classic: SDF
 
 Both Gazebo classic and Gazebo support [SDF](http://sdformat.org/)
 files to describe the simulation to be loaded. An SDF file defines the world

diff --git a/tutorials/migration_sensor_api.md b/tutorials/migration_sensor_api.md
@@ -1,6 +1,4 @@
-\page migrationsensorapi
-
-# Migration from Gazebo-classic: Sensor API
+\page migrationsensorapi Migration from Gazebo-classic: Sensor API
 
 When migrating plugins from Gazebo-classic to Gazebo, developers will
 notice that the C++ APIs for both simulators are quite different. Be sure to

diff --git a/tutorials/migration_world_api.md b/tutorials/migration_world_api.md
@@ -1,6 +1,4 @@
-\page migrationworldapi
-
-# Migration from Gazebo-classic: World API
+\page migrationworldapi Migration from Gazebo-classic: World API
 
 When migrating plugins from Gazebo-classic to Gazebo, developers will
 notice that the C++ APIs for both simulators are quite different. Be sure to

diff --git a/tutorials/resources.md b/tutorials/resources.md
@@ -33,8 +33,7 @@ System plugins may be loaded through:
 * Passing the shared library and class to be loaded through
   \ref gz::sim::ServerConfig::PluginInfo "PluginInfo"
   (within \ref gz::sim::ServerConfig "ServerConfig")
-  when instantiating the
-  \ref gz::sim::Server "Server"
+  when instantiating the \ref gz::sim::Server "Server".
 
 Gazebo will look for system plugins on the following paths, in order: