Merge branch 'caroltyk-tyk-operator' of https://github.com/TykTechnologies/tyk-docs into caroltyk-tyk-operator

Author: caroltyk

.github/pull_request_template.md

@@ -25,6 +25,7 @@
 <!-- Go over all the following points, and put an `x` in all the boxes that apply -->
 
 - [ ] I have added a **preview link** to the PR description.
+- [ ] I have reviewed the suggestions made by our AI (PR Agent) and updated them accordingly (spelling errors, rephrasing, etc.)
 - [ ] I have [reviewed the guidelines](https://github.com/TykTechnologies/tyk-docs/blob/master/CONTRIBUTING.md) for contributing to this repository.
 - [ ] I have [read the technical guidelines](https://github.com/TykTechnologies/tyk-docs/blob/master/CONTRIBUTING-TECHNICAL-GUIDE.md) for contributing to this repository.
 - [ ] Make sure you have started *your change* off *our latest `master`*.

tyk-docs/content/advanced-configuration/transform-traffic.md

@@ -1,7 +1,7 @@
 ---
 Title: Request and response middleware
 tags: ["middleware", "API request", "API response", "request processing", "response processing"]
-description: "An overview of Tyk's customisable request and response processing chain"
+description: "An overview of Tyk's customizable request and response processing chain"
 aliases:
   - /transform-traffic/endpoint-designer/
 ---
@@ -10,7 +10,7 @@ When you configure an API on Tyk, the Gateway will proxy all requests received a
 
 Within that chain are a highly configurable set of optional middleware that can, on a per-endpint basis:
 - apply processing to [API requests](#middleware-applied-to-the-api-request) before they are proxied to the upstream service
-- apply customisation to the [API response](#middleware-applied-to-the-api-response) prior to it being proxied back to the client
+- apply customization to the [API response](#middleware-applied-to-the-api-response) prior to it being proxied back to the client
 
 Tyk also supports a powerful custom plugin feature that enables you to add custom processing at different stages in the processing chains. For more details on custom plugins please see the [dedicated guide]({{< ref "plugins" >}}).
 

tyk-docs/content/advanced-configuration/transform-traffic/response-headers.md

@@ -19,7 +19,7 @@ There are related [Request Header Transform]({{< ref "transform-traffic/request-
 
 ## When to use response header transformation
 
-#### Customising responses for specific clients
+#### Customizing responses for specific clients
 
 A frequent use case for response header transformation is when a client requires specific headers for their application to function correctly. For example, a client may require a specific header to indicate the status of a request or to provide additional information about the response.
 

tyk-docs/content/api-management/manage-apis/tyk-oas-api-definition/tyk-oas-middleware.md

@@ -7,7 +7,7 @@ description: "Using middleware with Tyk OAS APIs"
 
 ### Introduction
 
-Tyk OAS APIs have access to an increasing range of Tyk middleware that you can configure to customise the handling of API requests and responses. In this guide we will show you how to enable some of these features in your Tyk OAS APIs.
+Tyk OAS APIs have access to an increasing range of Tyk middleware that you can configure to customize the handling of API requests and responses. In this guide we will show you how to enable some of these features in your Tyk OAS APIs.
 
 {{< note success >}}
 **Note**  

tyk-docs/content/basic-config-and-security/report-monitor-trigger-events/webhooks.md

@@ -13,7 +13,7 @@ aliases:
 
 ## Set up an Event Webhook with an API Definition
 
-In order to add extensibility and interoperability to Tyk, a new webhook event handler has been added. This allows a fixed payload (which can be customised) to be delivered to any open endpoint.
+In order to add extensibility and interoperability to Tyk, a new webhook event handler has been added. This allows a fixed payload (which can be customized) to be delivered to any open endpoint.
 
 The webhook handler allows the configuration of the method, body, header values, and target URL and makes use of Go templates to expose the event metadata.
 

tyk-docs/content/configure/outbound-email-configuration.md

@@ -101,16 +101,16 @@ If `SMTPUsername` or `SMTPPassword` is omitted, Tyk assumes that authentication
   "SecretAccessKey": "KEY"
 },
 ```
-### Customise your Welcome Emails
+### Customize your Welcome Emails
 
-You can customise the welcome email that a developer recieves when they signup to your portal. You can use images and other HTML formatted content. The following video walks you through the process.
+You can customize the welcome email that a developer recieves when they signup to your portal. You can use images and other HTML formatted content. The following video walks you through the process.
 
 {{< youtube XNyKRAlTDVs >}}
 
 
 1. Select **Settings** from your **Dashboard** > **Portal Management**
 2. You can change the from email address and the from email name for your welcome emails.
-3. To use customised email content, select **Enable custom welcome email**.
+3. To use customized email content, select **Enable custom welcome email**.
 4. You can then add the following custom content:
   * Email Subject
   * Email Body content
@@ -123,14 +123,14 @@ You can customise the welcome email that a developer recieves when they signup t
 6. Click **Save** at the top of the Portal Settings screen.
 
 
-### Customise your Key Approval Emails
+### Customize your Key Approval Emails
 
 #### Editing the Email Body
 
 1. Select **Settings** from your **Dashboard** > **Portal Management**
 2. From the "API Key approval email" section, select "Enable custom approval email", and edit the API Key email body.
 
-{{< img src="/img/2.10/key_approval_email_config.png" alt="Email-Customisation" >}}
+{{< img src="/img/2.10/key_approval_email_config.png" alt="Email-Customization" >}}
 
 #### Add an image or logo to the Key Approval Email
 
@@ -145,7 +145,7 @@ You can customise the welcome email that a developer recieves when they signup t
 The `LINK TO IMAGE` must be a publicly hosted resource.
 {{< /note >}}
 
-In an Self-Managed installation you have full access to the HTML template, allowing you further customisation.
+In an Self-Managed installation you have full access to the HTML template, allowing you further customization.
 
 #### Portal Manager Email Settings
 

tyk-docs/content/frequently-asked-questions/custom-developer-portal-options.md

@@ -9,6 +9,6 @@ weight: 0
 
 Use case: What if your developer portal is not exactly what I need?
 
-Sometimes our Tyk Gateway won't suit your exact needs.  Maybe you want to combine multiple Tyk installations under the same portal, or use your existing portal and add our functionality, or maybe customise the portal's branding per organisation?
+Sometimes our Tyk Gateway won't suit your exact needs.  Maybe you want to combine multiple Tyk installations under the same portal, or use your existing portal and add our functionality, or maybe customize the portal's branding per organisation?
 
 We have the ability to configure the portal to suit your needs. For details, including a video tutorial, see [Create a Custom Developer Portal]({{< ref "tyk-developer-portal/tyk-portal-classic/customise/custom-developer-portal" >}}).

tyk-docs/content/frequently-asked-questions/redis-persistence-using-containers.md

@@ -13,4 +13,4 @@ The Multi-Cloud Redis container is ephemeral, it isn't configured for persistenc
 
 If using Redis with Multi-Cloud we strongly recommend using an external Redis database.
 
-There are no settings for Redis available via environment variable, you would need to mount a new `redis.conf` into the container to customise the configuration, but again, we don't recommend it.
+There are no settings for Redis available via environment variable, you would need to mount a new `redis.conf` into the container to customize the configuration, but again, we don't recommend it.

tyk-docs/content/getting-started/key-concepts/api-catalogue.md

@@ -1,6 +1,6 @@
 ---
 date: 2017-03-23T13:02:38Z
-title: Portal API Catalogue
+title: Portal API Catalog
 menu:
   main:
     parent: "Key Concepts"
@@ -9,14 +9,14 @@ aliases:
   - /concepts/api-catalogue/
 ---
 
-The API Catalogue is part of the API Developer Portal of the Dashboard. It is the central place for you to manage which APIs your registered developers have access to.
+The API Catalog is part of the API Developer Portal of the Dashboard. It is the central place for you to manage which APIs your registered developers have access to.
 
-The API catalogue is completely separate from the regular API list section of the dashboard, as you may only wish to expose some of those APIs managed by Tyk to end users.
+The API catalog is completely separate from the regular API list section of the dashboard, as you may only wish to expose some of those APIs managed by Tyk to end users.
 
-API Catalogue entries are not actual directly tied to APIs in any way, they are connected to policies.
+API Catalog entries are not actual directly tied to APIs in any way, they are connected to policies.
 
 The reason for this is that policies can give access to a bundle of underlying APIs and therefore can represent a facade of services exposed as a single interface.
 
-The concept of the API Catalogue is that you publish what you wish your external APIs to appear as. So, for example, if you have a widgets API that is composed of 4 microservices (i.e. `/comments`, `/pricing`, `/details`, and `/SKU`), which are managed as four separate APIs in your Dashboard, but combined under a single Security Policy (so one token can access all four APIs), then you may not wish to have your users know these are microservices, they are just endpoints in your widgets API.
+The concept of the API Catalog is that you publish what you wish your external APIs to appear as. So, for example, if you have a widgets API that is composed of 4 microservices (i.e. `/comments`, `/pricing`, `/details`, and `/SKU`), which are managed as four separate APIs in your Dashboard, but combined under a single Security Policy (so one token can access all four APIs), then you may not wish to have your users know these are microservices, they are just endpoints in your widgets API.
 
 This approach allows you to separate "management" from "consumption" using a simple CMS-based bundling approach.

tyk-docs/content/getting-started/tutorials/publish-api.md

@@ -25,7 +25,7 @@ This is for the closed source [Tyk Developer Portal]({{< ref "tyk-developer-port
 {{< tab_end >}}
 {{< tab_start "Self-Managed" >}}
 
-## Add an API and Swagger based Docs to your Portal Catalogue
+## Add an API and Swagger based Docs to your Portal Catalog
 
 Managing your portal is a key part of Tyk Dashboard, this tutorial helps you get started working with your portal and publishing your APIs to your developers.
 
@@ -65,15 +65,15 @@ Save the policy by clicking **Create**.
 
 The API that you defined earlier is active and will work as you've seen in the previous tutorial, this time we want to use the Portal to generate a token for a named developer.
 
-Not all APIs are visible to the Portal, only the ones you tell it about, so from the **Catalogue** menu, select **Add API** then:
+Not all APIs are visible to the Portal, only the ones you tell it about, so from the **Catalog** menu, select **Add API** then:
 
 1.  Select your **Default** policy
 2.  Fill in the description fields
 3.  Ensure the **Enable this API** is selected
 
-Save the API Catalogue entry by clicking **Update**.
+Save the API Catalog entry by clicking **Update**.
 
-{{< img src="/img/2.10/portal_confirmation_on_prem.png" alt="Catalogue Entry" >}}
+{{< img src="/img/2.10/portal_confirmation_on_prem.png" alt="Catalog Entry" >}}
 
 ### Step 6: Set your Portal hostname
 

tyk-docs/content/planning-for-production/ensure-high-availability/enforced-timeouts.md

@@ -9,7 +9,7 @@ In any system, a task or operation takes a certain period of time to complete. W
 
 Tyk's Enforced Timeout middleware can be used to apply a maximum time that the Gateway will wait for a response before it terminates (or times out) the request. If the timeout expires, then Tyk will notify the client with an `HTTP 504 Gateway Timeout` error.
 
-This feature helps to maintain system stability and prevents unresponsive or long-running tasks from affecting the overall performance of the system. The enforced timeout can be customised and configured to suit specific requirements, providing control over resource allocation and ensuring optimal system functionality.
+This feature helps to maintain system stability and prevents unresponsive or long-running tasks from affecting the overall performance of the system. The enforced timeout can be customized and configured to suit specific requirements, providing control over resource allocation and ensuring optimal system functionality.
 
 ## When to use an enforced timeout
 

tyk-docs/content/plugins/supported-languages.md

@@ -78,7 +78,7 @@ The JavaScript Virtual Machine provides pluggable middleware that can modify a r
 *   **TCP Access**: The JSVM has no socket access so working with DB drivers and directly with Redis is not possible.
 
 ### Rich Plugins
-Rich Plugins can provide replacements for existing middleware functions (as opposed to augmentation) and are designed to be full-blown, optimized, highly capable services. They enable a full customised architecture to be built that integrates with a user's infrastructure.
+Rich Plugins can provide replacements for existing middleware functions (as opposed to augmentation) and are designed to be full-blown, optimized, highly capable services. They enable a full customized architecture to be built that integrates with a user's infrastructure.
 
 Rich Plugins bring about the following improvements:
 

tyk-docs/content/plugins/supported-languages/javascript-middleware.md

@@ -41,7 +41,7 @@ JavaScript functions are available globally in the same namespace. So, if you in
 
 The JavaScript Virtual Machine (JSVM) provided in the Gateway is a traditional ECMAScript5 compatible environment.
 
-Before you can use JavaScript customisation in any component you will need to enable the JSVM.
+Before you can use JavaScript customization in any component you will need to enable the JSVM.
 
 You do this by setting `enable_jsvm` to `true` in your `tyk.conf` [file]({{< ref "tyk-oss-gateway/configuration#enable_jsvm" >}}).
 

tyk-docs/content/plugins/supported-languages/javascript-middleware/middleware-scripting-guide.md

@@ -15,7 +15,7 @@ aliases:
     - /plugins/javascript-middleware/middleware-scripting-guide
 ---
 
-Tyk's JavaScript Virtual Machine (JSVM) provides a serverless compute function that allows for the execution of custom logic directly within the gateway itself. This can be accessed from [multiple locations]({{< ref "plugins/supported-languages/javascript-middleware" >}}) in the API processing chain and allows significant customisation and optimization of your request handling.
+Tyk's JavaScript Virtual Machine (JSVM) provides a serverless compute function that allows for the execution of custom logic directly within the gateway itself. This can be accessed from [multiple locations]({{< ref "plugins/supported-languages/javascript-middleware" >}}) in the API processing chain and allows significant customization and optimization of your request handling.
 
 In this guide we will cover the features and resources available to you when creating custom functions, highlighting where there are limitations for the different middleware stages.
 

tyk-docs/content/plugins/supported-languages/rich-plugins/grpc/custom-auth-python.md

@@ -5,7 +5,7 @@ title: "Create Custom Authentication Plugin With Python"
 
 In the realm of API security, HMAC-signed authentication serves as a foundational concept. In this developer-focused blog post, we'll use HMAC-signed authentication as the basis for learning how to write gRPC custom authentication plugins with Tyk Gateway. Why learn how to write Custom Authentication Plugins?
 
-- **Foundational knowledge**: Writing custom authentication plugins provides foundational knowledge of Tyk's extensibility and customisation capabilities.
+- **Foundational knowledge**: Writing custom authentication plugins provides foundational knowledge of Tyk's extensibility and customization capabilities.
 - **Practical experience**: Gain hands-on experience in implementing custom authentication logic tailored to specific use cases, starting with HMAC-signed authentication.
 - **Enhanced control**: Exercise greater control over authentication flows and response handling, empowering developers to implement advanced authentication mechanisms beyond built-in features.
 
@@ -655,7 +655,7 @@ While Tyk Gateway already supports HMAC-signed authentication out of the box, th
 
 It's important to note that the authentication mechanism implemented in this guide solely verifies the HMAC signature's validity and does not include access control checks against specific API resources. Developers should enhance this implementation by integrating access control logic to ensure authenticated requests have appropriate access permissions.
 
-By mastering the techniques outlined in this guide, developers are better equipped to address complex authentication challenges and build robust API security architectures using Tyk Gateway's extensibility features. This guide serves as a foundation for further exploration and experimentation with custom authentication plugins, empowering developers to innovate and customise API authentication solutions according to their unique requirements.
+By mastering the techniques outlined in this guide, developers are better equipped to address complex authentication challenges and build robust API security architectures using Tyk Gateway's extensibility features. This guide serves as a foundation for further exploration and experimentation with custom authentication plugins, empowering developers to innovate and customize API authentication solutions according to their unique requirements.
 
 ---
 

tyk-docs/content/plugins/supported-languages/rich-plugins/grpc/request-transformation-java.md

@@ -120,7 +120,7 @@ To generate the Protocol Buffers bindings we use the Gradle build task:
 gradle build
 ```
 
-If you need to customise any setting related to the bindings generation step, check the `build.gradle` file.
+If you need to customize any setting related to the bindings generation step, check the `build.gradle` file.
 
 ### Implement Server
 

tyk-docs/content/plugins/supported-languages/rich-plugins/grpc/write-grpc-plugin.md

@@ -16,11 +16,11 @@ This document serves as a developer's guide for understanding the key concepts a
 
 This comprehensive guide covers essential tasks, including:
 
-1. **Developing a gRPC Server:** Learn how to develop a gRPC server using [Tyk protocol buffers](https://github.com/TykTechnologies/tyk/tree/master/coprocess/proto). The gRPC server facilitates the execution of Tyk plugins, which offer custom middleware for various phases of the API request lifecycle. By integrating these plugins, developers can enable Tyk Gateway with enhanced control and flexibility in managing API requests, allowing for fine-grained customisation and tailored processing at each stage of the request lifecycle.
+1. **Developing a gRPC Server:** Learn how to develop a gRPC server using [Tyk protocol buffers](https://github.com/TykTechnologies/tyk/tree/master/coprocess/proto). The gRPC server facilitates the execution of Tyk plugins, which offer custom middleware for various phases of the API request lifecycle. By integrating these plugins, developers can enable Tyk Gateway with enhanced control and flexibility in managing API requests, allowing for fine-grained customization and tailored processing at each stage of the request lifecycle.
 
 2. **Configuring Tyk Gateway:** Set up Tyk Gateway to communicate with your gRPC Server and, optionally, an external secured web server hosting the gRPC plugin bundle for API configurations. Configure Tyk Gateway to fetch the bundle configured for an API from the web server, enabling seamless integration with gRPC plugins. Specify connection settings for streamlined integration.
 
-3. **API Configuration:** Customise API settings within Tyk Gateway to configure gRPC plugin utilization. Define plugin hooks directly within the API Definition or remotely via an external web server for seamless request orchestration. Tyk plugins provide custom middleware for different phases of the API request lifecycle, enhancing control and flexibility.
+3. **API Configuration:** Customize API settings within Tyk Gateway to configure gRPC plugin utilization. Define plugin hooks directly within the API Definition or remotely via an external web server for seamless request orchestration. Tyk plugins provide custom middleware for different phases of the API request lifecycle, enhancing control and flexibility.
 
 4. **API Testing:** Test that Tyk Gateway integrates with your gRPC server for the plugins configured for your API.