diff --git a/docs/book/how-to/trigger-pipelines/trigger-a-pipeline-from-rest-api.md b/docs/book/how-to/trigger-pipelines/trigger-a-pipeline-from-rest-api.md
index 24da9c88d14..969dfe4e6db 100644
--- a/docs/book/how-to/trigger-pipelines/trigger-a-pipeline-from-rest-api.md
+++ b/docs/book/how-to/trigger-pipelines/trigger-a-pipeline-from-rest-api.md
@@ -25,7 +25,7 @@ The above set of REST calls means that you can only trigger a pipeline that has
 ## A worked example
 
 {% hint style="info" %}
-Learn how to get a bearer token for the curl commands [here](../../reference/api-reference.md#using-a-bearer-token-to-access-the-api-programatically).
+Learn how to get a bearer token for the curl commands [here](../../reference/api-reference.md#using-a-bearer-token-to-access-the-api-programmatically).
 {% endhint %}
 
 Here is an example. Let's say would we like to re-run a pipeline called `training`. We first query the `/pipelines` endpoint:
diff --git a/docs/book/reference/api-reference.md b/docs/book/reference/api-reference.md
index d2ef27656bf..bc03677bc6e 100644
--- a/docs/book/reference/api-reference.md
+++ b/docs/book/reference/api-reference.md
@@ -15,10 +15,10 @@ In the local case (i.e. using `zenml up`, the docs are available on `http://127.
 
 ![ZenML API Redoc](../.gitbook/assets/zenml_api_redoc.png)
 
-## Using a bearer token to access the API programatically
+## Using a bearer token to access the API programmatically
 
 If you are using the ZenML server API using the above pages, it is enough to be logged in to your ZenML
-account in the same browser session. However, in order to do this programatically, the following steps
+account in the same browser session. However, in order to do this programmatically, the following steps
 need to be followed:
 
 1. Create a [service account](../how-to/connecting-to-zenml/connect-with-a-service-account.md):