diff --git a/docs/api/v3/chaining.md b/docs/api/v3/chaining.md
index 2d25610434f3bb4d54e05537a956b5bbfa9085b4..7719233eb9ed65c98bcefc23aa479879cf76ad45 100644
--- a/docs/api/v3/chaining.md
+++ b/docs/api/v3/chaining.md
@@ -1,6 +1,6 @@
 # APIv3 Chaining
 
-It is now possible to do two API calls at once with the first call feeding into the second. E.g. to create a contact with a contribution you can nest the contribution create into the contact create. Once the contact has been created it will action the contribution create using the id from the contact create as `contact_id`. Likewise you can ask for all activities or all contributions to be returned when you do a get.
+It is possible to do two API calls at once with the first call feeding into the second. E.g. to create a contact with a contribution you can nest the contribution create into the contact create. Once the contact has been created it will action the contribution create using the id from the contact create as `contact_id`. Likewise you can ask for all activities or all contributions to be returned when you do a `get`.
 
 See [api/v3/examples](https://github.com/civicrm/civicrm-core/tree/master/api/v3/examples) within the core source code for a plethora of examples (from unit tests) that use chaining. To start, look at these examples:
 
diff --git a/docs/api/v4/chaining.md b/docs/api/v4/chaining.md
index b1432bb48a9c94e40ee6c7c9c0c4ba65990a52bb..38171f48e8cb110f2f14480bb25080445cc0522c 100644
--- a/docs/api/v4/chaining.md
+++ b/docs/api/v4/chaining.md
@@ -1,6 +1,6 @@
 # APIv4 Chaining
 
-It is now possible to do two API calls at once with the first call feeding into the second. E.g. to create a contact with a contribution you can nest the contribution create into the contact create. Once the contact has been created it will action the contribution create using the id from the contact create as `contact_id`. Likewise you can ask for all activities or all contributions to be returned when you do a get.
+It is possible to do two API calls at once with the first call feeding into the second. E.g. to create a contact with a contribution you can nest the contribution create into the contact create. Once the contact has been created it will action the contribution create using the id from the contact create as `contact_id`. Likewise you can ask for all activities or all contributions to be returned when you do a `get`.
 
 Note that there are a few supported syntaxes:
 
@@ -31,7 +31,7 @@ civicrm_api('Contact', 'create', [
 ]);
 ```
 
-If you have 2 websites to create you can pass them as separate key => array pairs just specifiy a unique array key in the chain array
+If you have 2 websites to create you can pass them as separate key => array pairs just specify a unique array key in the chain array
 
 Object Oriented way
 
diff --git a/docs/api/v4/joins.md b/docs/api/v4/joins.md
index 5d281591cda95142ebd6f917eda6c942a07b24e9..1bbe0ea0c2bad9d4016538a4e60b78ccc2c778b5 100644
--- a/docs/api/v4/joins.md
+++ b/docs/api/v4/joins.md
@@ -10,7 +10,7 @@ To use a join in an API call, specify the name of the field on which the join ha
 
 For instance, to search for all primary emails, returning the email and joining to also return the contact's display name:
 
-Object oreinted way:
+Object Oriented way:
 
 ```php
 $result \Civi\Api4\Email::get()
@@ -38,7 +38,7 @@ $result = civicrm_api4('Email', 'get', [
 
 Alternatively, to return email addresses of everyone whose last name is Smith by joining to the Contact entity:
 
-Object oreinted way:
+Object Oriented way:
 
 ```php
 $result \Civi\Api4\Email::get()
@@ -61,7 +61,7 @@ $result = civicrm_api4('Email', 'get', [
 
 You can join multiple times in one query.  For instance, to return a list of events, displaying their name, the name of the related campaign, and that campaign's type:
 
-Object oreinted way:
+Object Oriented way:
 
 ```php
 $result \Civi\Api4\Email::get()
diff --git a/docs/core/pr-review.md b/docs/core/pr-review.md
index 73df9a41bd6cc8454669b6c8f575753a3b13c296..c72eae2e02b057527587c0ac5a10f4f07eedf6f8 100644
--- a/docs/core/pr-review.md
+++ b/docs/core/pr-review.md
@@ -46,7 +46,7 @@ On the PR, click over to “Files Changed” and understand what the code is doi
 
 ## Reproduce the problem
 
-Confirm which branch the PR was created against. This is probably either `master` or an Release Candidate branch. Setup an instance locally from that branch (e.g. with [buildkit](https://github.com/civicrm/civicrm-buildkit)), or test on the [public demo site if possible](https://civicrm.org/demo). Repeat the steps to reproduce described in the ticket or PR.
+Confirm which branch the PR was created against. This is probably either `master` or a Release Candidate branch. Setup an instance locally from that branch (e.g. with [buildkit](https://github.com/civicrm/civicrm-buildkit)), or test on the [public demo site if possible](https://civicrm.org/demo). Repeat the steps to reproduce described in the ticket or PR.
 
 Confirm that the issue was a problem and a problem “worth solving”, generally worthy of being in core.