diff --git a/doc/Roadmap.rst b/doc/Roadmap.rst
index 8405ee0c..31d43080 100644
--- a/doc/Roadmap.rst
+++ b/doc/Roadmap.rst
@@ -104,8 +104,7 @@ well with HoloViz include:
    -  `packed
       bubbles <https://stackoverflow.com/questions/46131572/making-a-non-overlapping-bubble-chart-in-matplotlib-circle-packing>`__
    -  `funnel charts <https://en.wikipedia.org/wiki/Funnel_chart>`__
-   -  `donut charts <https://datavizcatalogue.com/methods/donut_chart.html>`__ (which can be abused to make a `pie chart
-   <https://en.wikipedia.org/wiki/Pie_chart>`__ if you really want)
+   -  `donut charts <https://datavizcatalogue.com/methods/donut_chart.html>`__ (which can be abused to make a `pie chart <https://en.wikipedia.org/wiki/Pie_chart>`__ if you really want)
 
 7. **Interactive Matplotlib plotting**: Right now, HoloViews supports
    Matplotlib primarily as static PNG or SVG output. Matplotlib also
diff --git a/doc/about.rst b/doc/about.rst
index 7fc5ea36..3a40177e 100644
--- a/doc/about.rst
+++ b/doc/about.rst
@@ -83,22 +83,22 @@ HoloViz libraries have been supported by a variety of different funding mechanis
 Governance
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-The HoloViz governance has two levels - the HoloViz Organization 
-and the individual HoloViz Projects. This split allows us to stay aligned 
+The HoloViz governance has two levels - the HoloViz Organization
+and the individual HoloViz Projects. This split allows us to stay aligned
 as a community while supporting and benefiting from a diverse set of initiatives.
 
-The governing bodies at the HoloViz Organzation level are the Steering Committee 
-and Code of Conduct Committee. The Steering Committee is responsible for 
-higher-level aspects of the Organization, such as setting the overall scope, vision, 
+The governing bodies at the HoloViz Organization level are the Steering Committee
+and Code of Conduct Committee. The Steering Committee is responsible for
+higher-level aspects of the Organization, such as setting the overall scope, vision,
 policy, and direction. Read more about `Organization governance <https://github.com/holoviz/holoviz/blob/main/doc/governance/org-docs/CHARTER.md>`_.
 
 Each HoloViz Project may specify their own governance that is compatible with the HoloViz
-Organization governance. As an example of governance at the HoloViz Project level, 
-let's consider this HoloViz.org website Project. The governing body of this Project 
-is the Maintainers, one of which is the Project Director, and another may be the 
-Lead Maintainer. The Project Director is responsible for the overall direction and 
-scope of the Project while a Lead Maintainer is responsible for releases and 
-day-to-day technical management of the Project. Read more about the 
-`Project Governance <https://github.com/holoviz/holoviz/blob/main/doc/governance/project-docs/GOVERNANCE.md>`_, 
-or find the governance for other HoloViz Projects in the appropriate 
+Organization governance. As an example of governance at the HoloViz Project level,
+let's consider this HoloViz.org website Project. The governing body of this Project
+is the Maintainers, one of which is the Project Director, and another may be the
+Lead Maintainer. The Project Director is responsible for the overall direction and
+scope of the Project while a Lead Maintainer is responsible for releases and
+day-to-day technical management of the Project. Read more about the
+`Project Governance <https://github.com/holoviz/holoviz/blob/main/doc/governance/project-docs/GOVERNANCE.md>`_,
+or find the governance for other HoloViz Projects in the appropriate
 repository within the `HoloViz GitHub Organization <https://github.com/holoviz>`_.