diff --git a/doc/source/admin/hitachi_hnas_driver.rst b/doc/source/admin/hitachi_hnas_driver.rst
index ea0d71b4bf..5d64e491d0 100644
--- a/doc/source/admin/hitachi_hnas_driver.rst
+++ b/doc/source/admin/hitachi_hnas_driver.rst
@@ -227,9 +227,9 @@ if it exists is located in: */etc/neutron/plugins/openvswitch/ovs_neutron_plugin
 
 Create a route in HNAS to the tenant network. Please make sure
 multi-tenancy is enabled and routes are configured per EVS. Use the command
-“route-net-add” in HNAS console, where the network parameter should be the
+"route-net-add" in HNAS console, where the network parameter should be the
 tenant's private network, while the gateway parameter should be the flat
-network gateway and the “console-context --evs” parameter should be the ID of
+network gateway and the "console-context --evs" parameter should be the ID of
 EVS in use, such as in the following example:
 
 .. code-block:: console
diff --git a/doc/source/contributor/adding_release_notes.rst b/doc/source/contributor/adding_release_notes.rst
index f25345fc59..4d7bbcb812 100644
--- a/doc/source/contributor/adding_release_notes.rst
+++ b/doc/source/contributor/adding_release_notes.rst
@@ -57,7 +57,7 @@ How do I add a release note?
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 We use `Reno <https://docs.openstack.org/reno/latest/>`_ to create and manage
-release notes. The new subcommand combines a random suffix with a “slug” value
+release notes. The new subcommand combines a random suffix with a "slug" value
 to make the new file with a unique name that is easy to identify again later.
 To create a release note for your change, use: