diff --git a/website/content/docs/provisioning/ansible_intro.mdx b/website/content/docs/provisioning/ansible_intro.mdx
index 0c834840d..326a2b9a2 100644
--- a/website/content/docs/provisioning/ansible_intro.mdx
+++ b/website/content/docs/provisioning/ansible_intro.mdx
@@ -89,7 +89,9 @@ When using Ansible, it needs to know on which machines a given playbook should r
 
 The first and simplest option is to not provide one to Vagrant at all. Vagrant will generate an inventory file encompassing all of the virtual machines it manages, and use it for provisioning machines.
 
-#### Example with the [`ansible`](/vagrant/docs/provisioning/ansible) provisioner
+#### Ansible provisioner example
+
+Example with the [`ansible`](/vagrant/docs/provisioning/ansible) provisioner.
 
 ```text
 # Generated by Vagrant
@@ -100,7 +102,9 @@ default ansible_host=127.0.0.1 ansible_port=2200 ansible_user='vagrant' ansible_
 Note that the generated inventory file is stored as part of your local Vagrant environment in
 `.vagrant/provisioners/ansible/inventory/vagrant_ansible_inventory`.
 
-#### Example with the [`ansible_local`](/vagrant/docs/provisioning/ansible_local) provisioner
+#### Ansible local provision
+
+Example with the [`ansible_local`](/vagrant/docs/provisioning/ansible_local) provisioner
 
 ```text
 # Generated by Vagrant
diff --git a/website/content/vagrant-cloud/organizations/index.mdx b/website/content/vagrant-cloud/organizations/index.mdx
index 2856a08f6..3f7194426 100755
--- a/website/content/vagrant-cloud/organizations/index.mdx
+++ b/website/content/vagrant-cloud/organizations/index.mdx
@@ -1,6 +1,6 @@
 ---
 layout: vagrant-cloud
-page_page_title: Organizations in Vagrant Cloud
+page_title: Organizations in Vagrant Cloud
 ---
 
 ## Organizations in Vagrant Cloud