Links checked (carla-simulator#2661)

ArenBabikian · Mar 29, 2020 · f9fb1fe · f9fb1fe
1 parent c918f4b
commit f9fb1fe
Show file tree

Hide file tree

Showing 12 changed files with 82 additions and 83 deletions.
diff --git a/Docs/adv_recorder.md b/Docs/adv_recorder.md
@@ -5,7 +5,7 @@ This feature allows to record and reenact a previous simulation. All the events
 * [__Recording__](#recording)  
 * [__Simulation playback__](#simulation-playback)  
 	* Setting a time factor  
-* [__Recorded file__](#unreal-engine)  
+* [__Recorded file__](#recorded-file)  
 * [__Queries__](#queries)  
 	* Collisions  
 	* Blocked actors  

diff --git a/Docs/cont_contribution_guidelines.md b/Docs/cont_contribution_guidelines.md
@@ -18,7 +18,7 @@ issue is not already reported, and make sure you have read our
 
 [issueslink]: https://github.com/carla-simulator/carla/issues
 [docslink]: http://carla.readthedocs.io
-[faqlink]: http://carla.readthedocs.io/en/latest/faq/
+[faqlink]: build_faq.md
 
 ---
 ## Feature requests

diff --git a/Docs/core_actors.md b/Docs/core_actors.md
@@ -206,7 +206,7 @@ if traffic_light.get_state() == carla.TrafficLightState.Red:
 
 [__carla.Vehicle__](python_api.md#carla.Vehicle) are a special type of actor. They are remarkable for having better physics. This is achieved applying four types of different controls.  
 
-* __[carla.VehicleControl](python_api.md#carla.VehiclePhysicsControl)__ provides input for driving commands such as throttle, steering, brake, etc. 
+* __[carla.VehicleControl](python_api.md#carla.VehicleControl)__ provides input for driving commands such as throttle, steering, brake, etc. 
 ```py
 vehicle.apply_control(carla.VehicleControl(throttle=1.0, steer=-1.0))
 ```
@@ -247,8 +247,8 @@ vehicle.set_light_state(current_lights)
 
 [__carla.Walker__](python_api.md#carla.Walker) work in a similar way as vehicles do. Control over them is provided by controllers.  
 
-* [__carla.WalkerControl__](python_api.md#carla.Walker) moves the pedestrian around with a certain direction and speed. It also allows them to jump. 
-* [__carla.WalkerBoneControl__](python_api.md#carla.Walker) provides control over the 3D skeleton. [This tutorial](tuto_G_control_walker_skeletons.md) explains how to control it. 
+* [__carla.WalkerControl__](python_api.md#carla.WalkerControl) moves the pedestrian around with a certain direction and speed. It also allows them to jump. 
+* [__carla.WalkerBoneControl__](python_api.md#carla.WalkerBoneControl) provides control over the 3D skeleton. [This tutorial](tuto_G_control_walker_skeletons.md) explains how to control it. 
 
 Walkers can be AI controlled. They do not have an autopilot mode. The [__carla.WalkerAIController__](python_api.md#carla.WalkerAIController) actor moves around the actor it is attached to.  
 

diff --git a/Docs/core_map.md b/Docs/core_map.md
@@ -36,7 +36,7 @@ print(client.get_available_maps())
 
 The lane types defined by [OpenDRIVE standard 1.4](http://www.opendrive.org/docs/OpenDRIVEFormatSpecRev1.4H.pdf) are translated to the API in [__carla.LaneType__](python_api.md#carla.LaneType) as a series of enum values.  
 
-The lane markings surrounding a lane can be accessed through [__carla.LaneMarking__](python_api.md#carla.LaneMarkingType). These are defined with a series of variables.  
+The lane markings surrounding a lane can be accessed through [__carla.LaneMarking__](python_api.md#carla.LaneMarking). These are defined with a series of variables.  
 
 * [__carla.LaneMarkingType__](python_api.md#carla.LaneMarkingType) are enum values according to OpenDRIVE standards. 
 * [__carla.LaneMarkingColor__](python_api.md#carla.LaneMarkingColor) are enum values to determine the color of the marking. 
@@ -137,7 +137,7 @@ waypoint_list = map.generate_waypoints(2.0)
 waypoint_tuple_list = map.get_topology()
 ```
 
-* __Convert simulation point to geographical coordinates.__ Transforms a certain location to a [carla.Geolocation](python_api.md#carla.Geolocation) with latitude and longitude values. 
+* __Convert simulation point to geographical coordinates.__ Transforms a certain location to a [carla.GeoLocation](python_api.md#carla.GeoLocation) with latitude and longitude values. 
 ```py
 my_geolocation = map.transform_to_geolocation(vehicle.transform)
 ```

diff --git a/Docs/core_sensors.md b/Docs/core_sensors.md
@@ -209,7 +209,7 @@ Thus concludes the introduction to CARLA. However there is yet a lot to learn.
 
 <div class="build-buttons">
 <p>
-<a href="ref_code_recipes.md" target="_blank" class="btn btn-neutral" title="Code recipes">
+<a href="../ref_code_recipes" target="_blank" class="btn btn-neutral" title="Code recipes">
 Code recipes</a>
 </p>
 </div>
@@ -218,7 +218,7 @@ Code recipes</a>
 
 <div class="build-buttons">
 <p>
-<a href="adv_synchrony_timestep.md" target="_blank" class="btn btn-neutral" title="Synchrony and time-step">
+<a href="../adv_synchrony_timestep" target="_blank" class="btn btn-neutral" title="Synchrony and time-step">
 Synchrony and time-step</a>
 </p>
 </div>
@@ -227,7 +227,7 @@ Synchrony and time-step</a>
 
 <div class="build-buttons">
 <p>
-<a href="python_api.md" target="_blank" class="btn btn-neutral" title="Python API reference">
+<a href="../python_api" target="_blank" class="btn btn-neutral" title="Python API reference">
 Python API reference</a>
 </p>
 </div>

diff --git a/Docs/core_world.md b/Docs/core_world.md
@@ -2,7 +2,7 @@
 
 The client and the world are two of the fundamentals of CARLA, a necessary abstraction to operate the simulation and its actors.  
 
-This tutorial goes from defining the basics and creation of these elements, to describing their possibilities. If any doubt or issue arises during the reading, the [CARLA forum](forum.carla.org/) is there to solve them.  
+This tutorial goes from defining the basics and creation of these elements, to describing their possibilities. If any doubt or issue arises during the reading, the [CARLA forum](https://forum.carla.org/) is there to solve them.  
 
 * [__The client__](#the-client)
 	* Client creation

diff --git a/Docs/ros_installation.md b/Docs/ros_installation.md
@@ -14,7 +14,7 @@ The ROS bridge enables two-way communication between ROS and CARLA. The informat
 ### ROS Kinetic/Melodic
 
 *  __ROS Kinetic/Melodic.__ Install ROS [Melodic](http://wiki.ros.org/melodic/Installation/Ubuntu), for Ubuntu 18.04, or [Kinetic](http://wiki.ros.org/kinetic/Installation), for Ubuntu 16.04. ROS packages may be required, depending on the user needs. [rviz](http://wiki.ros.org/rviz) to visualize ROS data.  
-*  __CARLA 0.9.7 or later.__ Previous versions are not compatible with the ROS bridge. Follow the [quick start installation](../getting_started/quickstart) or make the build for the corresponding platform. 
+*  __CARLA 0.9.7 or later.__ Previous versions are not compatible with the ROS bridge. Follow the [quick start installation](start_quickstart.md) or make the build for the corresponding platform. 
 
 !!! Important
     Make sure that both CARLA and ROS work properly before continuing with the installation. 
@@ -132,7 +132,7 @@ To modify the way CARLA works along with the ROS bridge, edit [`share/carla_ros_
 	*  __If false (default).__ Data is published on every `world.on_tick()` and every `sensor.listen()` callbacks.  
 	*  __If true__ The bridge waits for all the sensor messages expected before the next tick. This might slow down the overall simulation but ensures reproducible results.  
 *  __Wait for vehicle command.__ In synchronous mode, pauses the tick until a vehicle control is completed. 
-*  __Simulation time-step.__ Simulation time (delta seconds) between simulation steps. __It must be lower than 0.1__. Take a look at the [documentation](../simulation_time_and_synchrony) to learn more about this.  
+*  __Simulation time-step.__ Simulation time (delta seconds) between simulation steps. __It must be lower than 0.1__. Take a look at the [documentation](adv_synchrony_timestep.md) to learn more about this.  
 *  __Role names for the Ego vehicles.__ Role names to identify ego vehicles. These will be controllable from ROS and thus, relevant topics will be created.  
 
 !!! Warning