Harmonize click link/button formatting

docs/articles/accounts/managing-account-members.md

@@ -8,7 +8,7 @@ manage users in your account.
 
 ## Add Account Member
 
-To start, navigate to the account settings page by clicking on your user icon in
+To start, navigate to the account settings page by clicking your user icon in
 the top right corner of the screen and selecting "Settings" from the dropdown
 menu.
 
@@ -40,6 +40,6 @@ the role from the drop down.
 
 ## Removing a Member
 
-To remove a user from the account, click on the remove icon next to the user.
+To remove a user from the account, click the remove icon next to the user.
 
 ![Remove Member](../../../public/media/managing-account-members/image-4.png)

docs/articles/accounts/managing-project-members.md

@@ -9,8 +9,8 @@ project level roles in order to grant them access to specific project resources.
 
 ## Add Project Member
 
-To manage project members, navigate to the project settings page and click on
-the "Members" tab. Here you can see a list of all members in the project and
+To manage project members, navigate to the project settings page and click 
+the **Members** tab, which shows a list of all members in the project and
 their roles.
 
 ![Project Members](../../../public/media/managing-project-members/image-1.png)

docs/articles/accounts/zuplo-api-keys.md

@@ -12,9 +12,9 @@ accessible areas such as GitHub repositories.
 
 ## Creating an API Key
 
-To start, navigate to the account settings page by clicking on your user icon in
+To start, navigate to the account settings page by clicking your user icon in
 the top right corner of the screen and selecting "Settings" from the dropdown
-menu. Click the "API Keys" tab to view the API keys in your account that you
+menu. Click the **API Keys** tab to view the API keys in your account that you
 have access to.
 
 ![API Keys](../../../public/media/zuplo-api-keys/image.png)
@@ -41,7 +41,7 @@ will need to create a new API key.
 ## Deleting an API Key
 
 API Keys can be deleted by selecting the delete button on the list page or by
-opening the details page for the key and clicking the "Delete" button at the
+opening the details page for the key and clicking the **Delete** button at the
 bottom of the page.
 
 ![Delete API Key](../../../public/media/zuplo-api-keys/image-2.png)

docs/articles/add-api-to-backstage.md

@@ -83,7 +83,7 @@ spec:
 ```
 
 You should now be able to see your API under the APIs tab in Backstage. If you
-navigate to your API and click the 'DEFINITION' tab - you can even preview your
+navigate to your API and click the **DEFINITION** tab - you can even preview your
 OpenAPI spec.
 
 ![OpenAPI spec](../../public/media/add-api-to-backstage/image-6.png)
@@ -126,7 +126,7 @@ Save and commit this file.
 ### 2/ Add your API Component to Backstage
 
 You can register existing APIs in your catalog directly from Backstage. Navigate
-to the APIs tab, and click 'REGISTER EXISTING API'.
+to the APIs tab, and click **REGISTER EXISTING API**.
 
 ![APIs list](../../public/media/add-api-to-backstage/image-5.png)
 

docs/articles/archiving-requests-to-storage.md

@@ -10,8 +10,8 @@ requests to Azure Blob Storage. We also have a post on
 
 First, let's set up Azure. You'll need a container in Azure storage
 ([docs](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-create?tabs=azure-portal)).
-Once you have your container you'll need the URL - you can get it on the
-`properties` tab of your container as shown below.
+Once you have your container you'll need the URL - click the
+**Properties** tab of your container as shown below.
 
 > **Note** - this sample is available as a Zup It on GitHub - just click ZupIt!
 > to deploy to your Zuplo account:

docs/articles/bonus-dynamic-rate-limiting.md

@@ -50,7 +50,7 @@ information to rate limit them differently.
 ## 2/ Add a Custom Code Module
 
 Navigate back to the Code tab. Now add a new module to the files section by
-clicking on the `+` next to the **modules** folder and choose new empty module.
+clicking the `+` next to the **modules** folder and choose new empty module.
 Name the module `rate-limit.ts`.
 
 ![New module](../../public/media/step-3-add-rate-limiting/image-3.png)
@@ -102,7 +102,7 @@ export function rateLimit(request: ZuploRequest, context: ZuploContext) {
 ## 3/ Update your Policy
 
 Now we'll reconfigure the rate-limiting policy to wire up our custom function.
-Find the policy in the **Route Designer** and click edit.
+Find the policy in the **Route Designer** and click **Edit**.
 
 ![Edit Policy](../../public/media/step-3-add-rate-limiting/image-4.png)
 

docs/articles/custom-ci-cd.md

@@ -26,7 +26,7 @@ following these steps:
 
 1. Navigate to [portal.zuplo.com](https://portal.zuplo.com) and log in.
 2. Select the account that you want to work on.
-3. Click on the "Settings" tab and navigate to the "API Keys" section.
+3. Click the **Settings** tab and navigate to the **API Keys** section.
 4. Write some tests for your API. We provide a rich set of test helpers and
    utils based on BDD. You can see examples of tests at
    [samples](https://github.com/zuplo/zup-cli-example-project/tree/main/tests).

docs/articles/custom-domains.md

@@ -23,7 +23,7 @@ for your Zuplo project.
 ### 1. Navigate to your project's Custom Domain Settings
 
 Go to your project in the Zuplo portal and open to the **Settings** tab (1),
-then select **Custom Domain** (2) and click on the `Add New Custom Domain`
+then select **Custom Domain** (2) and click the **Add New Custom Domain**
 button to open the `New Custom Domain` configuration modal.
 
 ![Custom Domain](../../public/media/custom-domains/image.png)

docs/articles/dev-portal-adding-pages.md

@@ -21,7 +21,7 @@ to get started. You can also create a new docs page via the new file button.
 ## Previewing Your Changes
 
 You can preview what your page will look like in the developer portal by
-clicking the 'Markdown Preview' tab above the editor.
+clicking the **Markdown Preview** tab above the editor.
 
 ![Markdown Preview](../../public/media/developer-portal/adding-pages/style-preview.png)
 

docs/articles/dev-portal-keycloak-auth.md

@@ -21,15 +21,15 @@ click "Next".
 
 In the Authentication flow section, enable the "Standard flow" and disable
 "Direct access grants". Leave "Client authentication" and "Authorization" set to
-"off". Click "Next".
+"off". Click **Next**.
 
 ![Client Capabilities](../../public/media/dev-portal-keycloak-auth/image-1.png)
 
 ### 3/ Set the Login Settings
 
 In the "Valid Redirect URIs" field, enter the URL of your Zuplo Dev Portal with
 the base path (this defaults to `/docs/`). Make sure you have the trailing slash
-set. Click "Save".
+set. Click **Save**.
 
 ![Login settings](../../public/media/dev-portal-keycloak-auth/image-3.png)
 
@@ -44,13 +44,13 @@ Dev Portal.
 
 ![JSON file](../../public/media/dev-portal-keycloak-auth/image-5.png)
 
-### 3/ Configure the Developer Portal
+### 5/ Configure the Developer Portal
 
 Inside of the Zuplo Developer portal navigate to the **Code Editor** tab and
 open the `dev-portal.json` file. Under the "Authentication" section, set the
 "Provider" to "OpenID Connect". Set the "Authority" value to the `issuer` value
 you copied from the JSON file in the previous step. Set the "Client ID" value to
 the value you set in step 1 (in our example this is `zuplo-dev-portal`). Click
-"Save".
+**Save**.
 
 ![developer portal settings](../../public/media/dev-portal-keycloak-auth/image-6.png)

docs/articles/dev-portal-supabase-auth.md

@@ -93,8 +93,8 @@ Or in the JSON file:
 
 Before we leave the Zuplo Portal, you’ll need to grab your Zuplo API key. This
 key is used to securely connect your Supabase Auth App with the Developer
-Portal. From the side nav, go to your Project Settings and then click on Zuplo
-API Keys. Copy your API key.
+Portal. From the side nav, go to your Project Settings and then click **Zuplo
+API Keys**. Copy your API key.
 
 ![img](../../public/media/supabase-auth/copy-key-updated.png)
 
@@ -381,10 +381,10 @@ to sign into your Supabase project via the Developer Portal
    ```
 
 5. Deploy your code (make sure to set an environment variable for you
-   ZUPLO_API_KEY) and navigate to your Dev Portal. Then click the “Sign In”
+   ZUPLO_API_KEY) and navigate to your Dev Portal. Then click the **Sign In**
    button
 6. You should be redirected to your Supabase Auth App. Enter the email and
-   password of an existing user and click “Sign In”.
+   password of an existing user and click **Sign In**.
 7. You will be redirected back to the Dev portal and be signed into your
    Supabase account!
 
@@ -414,7 +414,7 @@ how to sign them out.
    ```
 
 2. Deploy your code and navigate to your Dev Portal. Sign in if you aren’t
-   already. Then click your user icon and “Logout”
+   already. Then click your user icon and **Logout**
 
 3. You should now be signed out of your Supabase Account
 
@@ -490,9 +490,9 @@ need to have completed the Sign Up Support section above first**
 
    You should now see a GitHub button on your login page
 
-4. Deploy your code and navigate to your Dev Portal. Then click the “Sign In”
+4. Deploy your code and navigate to your Dev Portal. Then click the **Sign In**
    button
-5. You should be redirected to your Supabase Auth App. Click the “GitHub” button
+5. You should be redirected to your Supabase Auth App. Click the **GitHub** button
 6. You will be redirected to the GitHub OAuth flow. Sign into GitHub if you
    aren’t already, and navigate through the flow
 7. You will be redirected back to the Dev portal and be signed into your GitHub

docs/articles/local-development-debugging.md

@@ -33,7 +33,7 @@ npx @zuplo/cli dev --debug-port 9229
 ```
 
 3. Switch to the View > Run and Debug in VS Code. You can now attach the
-   debugger by selecting "Zuplo Gateway" and clicking the green triangle.
+   debugger by selecting **Zuplo Gateway** and clicking the green triangle.
 
 ![VS code debugging](../../public/media/local-development-debugging/image.png)
 

docs/articles/open-api.md

@@ -13,7 +13,7 @@ your default OpenAPI routing file (oas = 'open api specification').
 You can use the Route Designer to build your routes, which will be creating an
 OpenAPI document in the background for you (check it out in the **JSON View**).
 
-You can also **import an OpenAPI** document by clicking on the **Open API** tab.
+You can also **import an OpenAPI** document by clicking the **Open API** tab.
 
 ![Import Open API](../../public/media/open-api/image-1.png)
 

docs/articles/rename-or-move-project.md

@@ -26,7 +26,7 @@ correct name. Choose the `Advanced` option on the new project dialog.
 ![Import existing project](../../public/media/source-control/image-1.png)
 
 You should see a list of Orgs and Repos - pick the source repo you wanted to
-move and click Create Project from Repository.
+move and click **Create Project from Repository**.
 
 Your new project will now be connected to this repo and ready to go.
 

docs/articles/step-1-setup-basic-gateway.md

@@ -40,7 +40,7 @@ quick overview of them:
 ![Your First Route](../../public/media/step-1-setup-basic-gateway/image-14.png)
 
 Save your new route (you can click the three-dot menu next to `routes.oas.json`
-and then click Save, or press CMD+S).
+and then click **Save**, or press **CMD+S**).
 
 You can quickly test this route by clicking the **Test** button next to the
 **Path** field. You can use the built in test tool or click the URL to open in a

docs/articles/step-2-add-rate-limiting.md

@@ -34,7 +34,7 @@ pipeline.
 
 ![Add policy](../../public/media/step-2-add-rate-limiting/image.png)
 
-Search for the rate limiting policy (not the "Complex" one) and click on it!
+Search for the rate limiting policy (not the "Complex" one) and click it.
 
 ![Add rate-limiting policy](../../public/media/step-2-add-rate-limiting/image-2.png)
 
@@ -45,7 +45,7 @@ rest of the policy's documentation and configuration in the right panel.
 
 ![Rate limiting policy](../../public/media/step-2-add-rate-limiting/image-3.png)
 
-Click 'OK' to apply the policy, and then save your changes to redeploy.
+To apply the policy, click **OK**. Then, save your changes to redeploy.
 
 ## 2/ Testing your Policy
 
@@ -62,8 +62,8 @@ Your rate limiting policy is now intercepting excess requests, protecting the
 Whenever you deploy a new endpoint on Zuplo, it will automatically be added to
 your [autogenerated developer documentation portal](./developer-portal.md).
 
-To access your API's developer portal, click the "Gateway deployed" button in
-your toolbar and click on the link under Developer Portal.
+To access your API's developer portal, click the **Gateway deployed** button in
+your toolbar and click the link under Developer Portal.
 ![Developer portal menu](../../public/media/step-2-add-rate-limiting/image-5.png)
 You can also find this link in the Getting Started section of the portal, every
 time you navigate to your project.

docs/articles/step-3-add-api-key-auth.md

@@ -56,7 +56,7 @@ If you test your route, you should get a 401 Unauthorized response
 ## 2/ Set up an API Key
 
 In order to call your API, you need to configure an API consumer. Go to
-**Services**, then click "Configure" on the "API Key Service".
+**Services**, then click **Configure** on the "API Key Service".
 
 ![API Key Service](../../public/media/step-3-add-api-key-auth/image-2.png)
 
@@ -74,15 +74,15 @@ Let's break down the configuration needed.
   plan, organization, etc.
 
 Go ahead and fill in `test-consumer` for the Subject. Add your own email as a
-Key manager, and leave the metadata empty for now. Click 'Save consumer' once
+Key manager, and leave the metadata empty for now. Click **Save consumer** once
 you're done.
 
 ![New Consumer](../../public/media/step-3-add-api-key-auth/image-3.png)
 
 ## 3/ Copy your API Key
 
-After your API Key consumer is created, click the copy button (next to the eye
-icon) to copy your new API Key.
+After your API Key consumer is created, copy your new API Key by clicking the copy button (next to the eye
+icon).
 
 ![Copy Key](../../public/media/step-3-add-api-key-auth/image-4.png)
 
@@ -115,8 +115,8 @@ management into your existing dashboard. See
 Whenever you deploy a new endpoint on Zuplo, it will automatically be added to
 your [autogenerated developer documentation portal](./developer-portal.md).
 
-To access your API's developer portal, click the "Gateway deployed" button in
-your toolbar and click on the link under Developer Portal.
+To access your API's developer portal, click the **Gateway deployed** button in
+your toolbar and click the link under Developer Portal.
 ![Developer portal menu](../../public/media/step-2-add-rate-limiting/image-5.png)
 
 When you use certain policies like API keys, Zuplo will document properties like

docs/articles/step-4-deploying-to-the-edge.md

@@ -150,7 +150,7 @@ environment we want to update first). Click **Create pull request**.
 
 ![GitHub PR](https://cdn.zuplo.com/assets/875b164d-b7ef-4f46-9cdb-8d59354b5b93.png)
 
-When ready, click **Merge pull request**
+When ready, click **Merge pull request**.
 
 ![Merge PR](https://cdn.zuplo.com/assets/e8c68072-35dc-462a-8161-7a44e40fa1df.png)
 

docs/articles/testing-graphql.md

@@ -16,7 +16,7 @@ API Test Console.
 3. Convert your GraphQL Query and GraphQL Variables into a JSON body. You can
    use [this tool](https://datafetcher.com/graphql-json-body-converter) to do so
    easily
-4. Paste the JSON Body into the test's Body field and click the Test button
+4. Paste the JSON Body into the test's Body field and click the **Test** button
 
 ![Docs Folder](../../public/media/guides/testing-graphql/test-request.png)
 

docs/cli/authentication.md

@@ -15,7 +15,7 @@ by following these steps:
 
 1. Navigate to [portal.zuplo.com](https://portal.zuplo.com) and log in.
 2. Select the account that you want to work on.
-3. Click on the "Settings" tab and navigate to the "API Keys" section. Select an
+3. Click the **Settings** tab and navigate to the "API Keys" section. Select an
    existing API Key or create a new one to use with the CLI.
 
 Most commands take an `--api-key` argument. For example, to list your available