diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index c1cce2195..e20976ae1 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -3,7 +3,7 @@
Please explain the changes you made, including a reference to the related issue if applicable
### Checklist
-- [ ] **Required by CI**: Code is auto formatted using [clang-format](http://moveit.ros.org/documentation/contributing/code)
+- [ ] **Required by CI**: Code is auto formatted using [clang-format](http://moveit.ai/documentation/contributing/code)
- [ ] While waiting for someone to review your request, please consider reviewing [another open pull request](https://github.com/moveit/moveit/pulls) to support the maintainers
[//]: # "You can expect a response from a maintainer within 7 days. If you haven't heard anything by then, feel free to ping the thread. Thank you!"
diff --git a/README.md b/README.md
index 13c652048..cdbe09a65 100644
--- a/README.md
+++ b/README.md
@@ -47,7 +47,7 @@ We rely on the community to keep these tutorials up-to-date and bug-free. If you
**Code Formatting**
-* These tutorials use the same [style guidelines](http://moveit.ros.org/documentation/contributing/code/) as the MoveIt project. When modifying or adding to these tutorials, it is required that code is auto-formatted using [clang-format](http://moveit.ros.org/documentation/contributing/code/). To check and apply the style guidelines we use [pre-commit](https://pre-commit.com/).
+* These tutorials use the same [style guidelines](http://moveit.ai/documentation/contributing/code/) as the MoveIt project. When modifying or adding to these tutorials, it is required that code is auto-formatted using [clang-format](http://moveit.ai/documentation/contributing/code/). To check and apply the style guidelines we use [pre-commit](https://pre-commit.com/).
* Tutorials should exemplify best coding practices. If a contribution wouldn't pass review in the MoveIt project, then it shouldn't pass review in the tutorials.
* Relevant code should be included and explained using the ``.. tutorial-formatter::`` tag.
* Irrelevant code should be excluded from the generated HTML using the ``BEGIN_TUTORIAL``, ``END_TUTORIAL``, ``BEGIN_SUB_TUTORIAL``, and ``END_SUB_TUTORIAL`` tags.
diff --git a/_themes/sphinx_rtd_theme/breadcrumbs.html b/_themes/sphinx_rtd_theme/breadcrumbs.html
index 51482c5be..19fdb3da1 100644
--- a/_themes/sphinx_rtd_theme/breadcrumbs.html
+++ b/_themes/sphinx_rtd_theme/breadcrumbs.html
@@ -13,7 +13,7 @@
{% endif %}
{% endif %}
-
MoveIt »
+ MoveIt »
Tutorials »
{% for doc in parents %}
{{ doc.title }} »
diff --git a/_themes/sphinx_rtd_theme/layout.html b/_themes/sphinx_rtd_theme/layout.html
index f90bef074..e171970d8 100644
--- a/_themes/sphinx_rtd_theme/layout.html
+++ b/_themes/sphinx_rtd_theme/layout.html
@@ -98,7 +98,7 @@
{% block sidebartitle %}
-
+
diff --git a/conf.py b/conf.py
index 8dce83d66..1494e0e8d 100644
--- a/conf.py
+++ b/conf.py
@@ -117,7 +117,7 @@
"http://docs.ros.org/" + ros_distro + "/api/moveit_core/html/%s.html",
"",
),
- "moveit_website": ("http://moveit.ros.org/%s/", ""),
+ "moveit_website": ("http://moveit.ai/%s/", ""),
"locked_planning_scene": (
"http://docs.ros.org/"
+ ros_distro
diff --git a/doc/ompl_interface/ompl_interface_tutorial.rst b/doc/ompl_interface/ompl_interface_tutorial.rst
index 5ad98c800..533e1e685 100644
--- a/doc/ompl_interface/ompl_interface_tutorial.rst
+++ b/doc/ompl_interface/ompl_interface_tutorial.rst
@@ -130,7 +130,7 @@ You can adjust the amount of time MoveIt spends on smoothing by increasing the p
Although not currently exposed at the top levels of MoveIt (TODO), more smoothing can be accomplished by setting the simplification duration to 0 (unlimited) in ``model_based_planning_context.cpp``. This will enable OMPL's ``simplifyMax()`` function.
-Besides the internal OMPL smoothers, recent efforts have been made to do post-proccessing with STOMP/CHOMP. See `this blog post
`_.
+Besides the internal OMPL smoothers, recent efforts have been made to do post-proccessing with STOMP/CHOMP. See `this blog post `_.
Persistent Roadmaps
-------------------
diff --git a/doc/planning_adapters/planning_adapters_tutorial.rst b/doc/planning_adapters/planning_adapters_tutorial.rst
index 557e88b14..5dc586bce 100644
--- a/doc/planning_adapters/planning_adapters_tutorial.rst
+++ b/doc/planning_adapters/planning_adapters_tutorial.rst
@@ -21,7 +21,7 @@ As you add and remove packages from your workspace you will need to clean your w
cd ~/ws_moveit/src
catkin clean
-Now follow the instructions on the MoveIt homepage for `installing MoveIt Melodic from source `_. Note that you can skip the **Prerequisites** section since you should already have a Catkin workspace.
+Now follow the instructions on the MoveIt homepage for `installing MoveIt Melodic from source `_. Note that you can skip the **Prerequisites** section since you should already have a Catkin workspace.
Re-source the setup files: ::
diff --git a/index.rst b/index.rst
index f71272541..2854d7b43 100644
--- a/index.rst
+++ b/index.rst
@@ -6,7 +6,7 @@ These tutorials will quickly get you, and your robot, using the MoveIt Motion Pl
.. image:: doc/quickstart_in_rviz/rviz_plugin_head.png
:width: 700px
-In these tutorials, the Franka Emika Panda robot is used as a quick-start demo. Alternatively, you can easily use any robot that has already been configured to work with MoveIt - check the `list of robots running MoveIt `_ to see whether MoveIt is already available for your robot. Otherwise, you can setup MoveIt to work with your custom robot in the tutorial section "Integration with a New Robot", below.
+In these tutorials, the Franka Emika Panda robot is used as a quick-start demo. Alternatively, you can easily use any robot that has already been configured to work with MoveIt - check the `list of robots running MoveIt `_ to see whether MoveIt is already available for your robot. Otherwise, you can setup MoveIt to work with your custom robot in the tutorial section "Integration with a New Robot", below.
Getting Started with MoveIt and RViz
-------------------------------------
@@ -55,7 +55,7 @@ Building more complex applications with MoveIt often requires developers to dig
Integration with a New Robot
----------------------------
-Before attempting to integrate a new robot with MoveIt, check whether your robot has already been setup (see the `list of robots running MoveIt `_). Otherwise, follow the tutorials in this section to integrate your robot with MoveIt (and share your results on the MoveIt Discourse Channel)
+Before attempting to integrate a new robot with MoveIt, check whether your robot has already been setup (see the `list of robots running MoveIt `_). Otherwise, follow the tutorials in this section to integrate your robot with MoveIt (and share your results on the MoveIt Discourse Channel)
.. toctree::
:maxdepth: 1
@@ -103,7 +103,7 @@ Attribution
-----------
Major contributors to the MoveIt tutorials are listed in chronological order: Sachin Chitta, Dave Hershberger, Acorn Pooley, Dave Coleman, Michael Gorner, Francisco Suarez, Mike Lautman. Help us improve these docs and we'll be happy to include you here also!
-The tutorials had a major update in 2018 during a code sprint sponsored by Franka Emika in collaboration with PickNik (`Check out the blog post! `_)
+The tutorials had a major update in 2018 during a code sprint sponsored by Franka Emika in collaboration with PickNik (`Check out the blog post! `_)
.. image:: ./_static/franka_logo.png
:width: 300px