Merge branch 'master' of https://github.com/TykTechnologies/tyk-docs into contribution-guide

Author: sharadregoti

CONTRIBUTING.md

@@ -55,7 +55,7 @@ We have created a few guidelines to help with creating PR. To make sure these re
    2. Check the `PR Agent` bot for any important suggestions, spelling mistakes or typos
    3. The `PR Agent` bot creates a description for you. If needed, please add more info to it. Link to a GitHub issue if it exists.
 
-### Pull Request Review Schedule
+#### Pull Request Review Schedule
 
 PRs will be reviewed weekly, every Tuesday and Thursday. New reviews will be
 reviewed on Tuesdays and review responses will be done on Thursdays.

tyk-docs/content/api-management/gateway-config-managing-oas.md

@@ -673,7 +673,7 @@ To update just the OpenAPI description of your API in Tyk, you simply send the O
 | Body         | OpenAPI document                         |
 | Parameters   | Path: `{API-ID}`                         |
 
-You need to specify which API to update - and so so using the `API-ID` value from the response you received from Tyk when creating the API. You can find this in the `x-tyk-api-gateway.info.id` field of the Tyk OAS API Definition stored in your main storage.
+You need to specify which API to update - and do so using the `API-ID` value from the response you received from Tyk when creating the API. You can find this in the `x-tyk-api-gateway.info.id` field of the Tyk OAS API Definition stored in your main storage.
 
 **Applying an Updated Tyk OAS API Definition** 
 
@@ -687,7 +687,7 @@ To update the whole API in Tyk, you simply send the Tyk OAS API definition in th
 | Body         | Tyk OAS API Definition                   |
 | Parameters   | Path: `{API-ID}`                         |
 
-You need to specify which API to update - and so so using the `API-ID` value from the response you received from Tyk when creating the API. You can find this in the `x-tyk-api-gateway.info.id` field of the Tyk OAS API Definition stored in your main storage.
+You need to specify which API to update - and do so using the `API-ID` value from the response you received from Tyk when creating the API. You can find this in the `x-tyk-api-gateway.info.id` field of the Tyk OAS API Definition stored in your main storage.
 
 **Check request response**
 
@@ -724,7 +724,7 @@ To update just the OpenAPI description of your API in Tyk, you simply send the O
 | Body         | OpenAPI document                         |
 | Parameters   | Path: `{API-ID}`  Query: `templateId`    |
 
-You need to specify which API to update - and so so using the `API-ID` value from the response you received from Tyk when creating the API. You can find this in the `x-tyk-api-gateway.info.id` field of the Tyk OAS API Definition that Tyk has stored in the `/apps` folder of your Tyk Gateway installation.
+You need to specify which API to update - and do so using the `API-ID` value from the response you received from Tyk when creating the API. You can find this in the `x-tyk-api-gateway.info.id` field of the Tyk OAS API Definition that Tyk has stored in the `/apps` folder of your Tyk Gateway installation.
 
 
 **Applying an Updated Tyk OAS API Definition** 
@@ -739,7 +739,7 @@ To update the whole API in Tyk, you simply send the Tyk OAS API definition in th
 | Body         | Tyk OAS API Definition                   |
 | Parameters   | Path: `{API-ID}`                         |
 
-You need to specify which API to update - and so so using the `API-ID` value from the response you received from Tyk when creating the API. You can find this in the `x-tyk-api-gateway.info.id` field of the Tyk OAS API Definition that Tyk has stored in the `/apps` folder of your Tyk Gateway installation.
+You need to specify which API to update - and do so using the `API-ID` value from the response you received from Tyk when creating the API. You can find this in the `x-tyk-api-gateway.info.id` field of the Tyk OAS API Definition that Tyk has stored in the `/apps` folder of your Tyk Gateway installation.
 
 
 **Check request response**

tyk-docs/content/api-management/graphql.md

@@ -284,7 +284,7 @@ In order to complete the next steps, you need to have the [Tyk OSS]({{< ref "tyk
 
 #### Creation Methods
 
-With Tyk OSS, it is possible to create GQL APIs using Tyk's Gateway API or to generate a file with the same object and store it in the `/apps` folder of the Tyk Gateway installation folder. This is demonstrated [here]({{< ref "api-management/manage-apis/deploy-apis/deploy-apis-overview#file-based-configurations" >}}).
+With Tyk OSS, it is possible to create GQL APIs using Tyk's Gateway API or to generate a file with the same object and store it in the `/apps` folder of the Tyk Gateway installation folder. This is demonstrated [in the file-based configuration section]({{< ref "api-management/manage-apis/deploy-apis/deploy-apis-overview#file-based-configuration" >}}).
 
 
 #### Steps for Configuration

tyk-docs/content/api-management/manage-apis/deploy-apis/deploy-apis-overview.md

@@ -1,57 +1,55 @@
 ---
-title: API Deployment Methods
+title: API Creation Methods
 date: 2023-09-04
-description: "Explains deployment methods for Tyk APIs"
-tags: [ "API Deployment", "API", "Deployment", "Deployment Methods", "Deploy APIs", "Tyk Sync", "Tyk Operator" ]
+description: "Different ways to create and manage APIs in Tyk"
+tags: [ "API Management", "API Configuration", "Dashboard", "Tyk Sync", "Tyk Operator" ]
 ---
 
-At Tyk, we provide various deployment methods to suit different stages of your API development lifecycle. Each option offers unique features and capabilities tailored to your specific needs.
+This page explains the different methods available for creating and managing APIs in Tyk, each suited to different use cases and workflow requirements.
 
-## File-based Configurations
+## File-based configuration {#file-based-configuration}
 
-For Open Source users, the File-based Configurations option offers a quick way to test your gateway and API configurations using a JSON API specification. Simply load the configuration to the `/apps` folder, making it easy to experiment with different setups.
+Load API configurations directly to the `/apps` folder using JSON API specifications. This method is available for open source users and is ideal for testing gateway and API configurations.
 
-Usage: Recommended for testing gateway and API configurations in an Open Source environment.
+**Use case:** Testing and experimentation in development environments.
 
-Learn more:
-* [Tutorial: Create an API in File-based Mode]({{< ref "api-management/gateway-config-managing-classic#create-an-api-in-file-based-mode" >}})
+**Learn more:**
+* [Create an API in file-based mode]({{< ref "api-management/gateway-config-managing-classic#create-an-api-in-file-based-mode" >}})
 
 ## Dashboard UI
 
-The Dashboard UI is ideal for Trial / POC users and anyone looking to experiment with Tyk features. It offers a user-friendly web GUI that allows you to import, create, and configure APIs easily. Changes made through the Dashboard UI take effect instantly, making it suitable for learning, testing, and Proof of Concept (PoC) purposes.
+Create and configure APIs through the web-based Dashboard interface. Changes take effect immediately, making this method suitable for learning, testing, and proof-of-concept work.
 
-Usage: Recommended for PoC, learning, or manual testing; not intended for automation.
+**Use case:** Manual API management, learning, and proof-of-concept projects.
 
-Learn more:
-* [Tutorial: Create an API with the Dashboard]({{< ref "api-management/gateway-config-managing-classic#create-an-api-with-the-dashboard" >}})
+**Learn more:**
+* [Create an API with the Dashboard]({{< ref "api-management/gateway-config-managing-classic#create-an-api-with-the-dashboard" >}})
 
-## Dashboard or Gateway API
+## Dashboard and Gateway API
 
-For programmatic control, both Tyk Pro users and Open Source users can leverage either the Dashboard API or the Gateway API. These APIs enable the creation and management of APIs, Policies, Keys, Developer Portals, and more. They provide the flexibility to automate some API operations, but it involves an imperative approach and may not be as straightforward for repetitive tasks across different environments.
+Programmatically create and manage APIs, policies, keys, and developer portals using REST APIs. This method provides flexibility for automation but requires imperative scripting.
 
-Usage: Suitable for those who require programmatic control over API management, APIs, Policies, and other aspects of Tyk.
+**Use case:** Programmatic API management and basic automation needs.
 
-Learn more:
+**Learn more:**
 - [Dashboard API]({{< ref "api-management/dashboard-configuration#exploring-the-dashboard-api" >}})
 - [Gateway API]({{< ref "tyk-gateway-api" >}})
 
 ## Tyk Sync
 
-Tyk Sync enables declarative API management and GitOps. With Tyk Sync, you can manage API configurations in a transportable format, which can be version controlled using Git. This approach allows you to achieve automation in the API deployment process and maintain a source of truth for API configurations. By setting up a CI/CD pipeline, changes made in Git trigger the reload of configurations in Tyk Dashboard.
+Manage API configurations declaratively using version-controlled files. Tyk Sync enables GitOps workflows by maintaining API configurations as code that can be versioned and deployed through CI/CD pipelines.
 
-Usage: Recommended for organizations looking to implement GitOps in API management and have portable API and Policy configurations.
+**Use case:** GitOps workflows and teams requiring version-controlled API configurations.
 
-Learn more:
+**Learn more:**
 - [Tyk Sync]({{< ref "api-management/automations/sync" >}})
 
 ## Tyk Operator
 
-Building on the capabilities of Tyk Sync and GitOps, Tyk Operator provides a powerful solution for declarative API management and constant reconciliation in dynamic environments. Leveraging Kubernetes features, Tyk Operator treats APIs and Policies as Custom Resources, allowing drift detection and automatic reconciliation. It ensures that the desired state stored in Git matches the actual state in the Tyk instance, enabling seamless management of Tyk APIs and Policies alongside other Kubernetes resources.
+Kubernetes-native API management using Custom Resource Definitions (CRDs). Tyk Operator provides declarative configuration with automatic drift detection and reconciliation in Kubernetes environments.
 
-Usage: Recommended for organizations already running Kubernetes and seeking a Kubernetes-native, automated approach to API deployment and management.
+**Use case:** Kubernetes-native environments requiring automated API lifecycle management.
 
-Learn more:
+**Learn more:**
 - [Tyk Operator]({{< ref "api-management/automations/operator#what-is-tyk-operator" >}})
-- [Using Tyk Operator to enable GitOps with Tyk]({{< ref "api-management/automations" >}})
-
-With these flexible deployment options, you can easily design, develop, and deploy APIs in Tyk according to your specific requirements and workflow. Choose the option that best aligns with your needs and integrates smoothly into your API development lifecycle.
+- [Using Tyk Operator to enable GitOps]({{< ref "api-management/automations" >}})

tyk-docs/content/api-management/migrate-from-tyk-classic.md

@@ -1,5 +1,5 @@
 ---
-title: "Migrating from Tyk Classic"
+title: "Migrating from Tyk Classic APIs"
 date: 2025-02-10
 tags: ["Tyk OAS API", "Tyk Classic API", "Migrate", "Convert", "Migration", "Tyk Classic", "Tyk OAS", "API definition"]
 keywords: ["Tyk OAS API", "Tyk Classic API", "Migrate", "Convert", "Migration", "Tyk Classic", "Tyk OAS", "API definition"]

tyk-docs/content/api-management/plugins/rich-plugins.md

@@ -1232,7 +1232,7 @@ Your *Dispatch* RPC should handle the request made by Tyk Gateway, implementing
 
 Consult the [Tyk protocol buffers](https://github.com/TykTechnologies/tyk/tree/master/coprocess/proto) for the definition of the service and data structures that enable integration of Tyk gateway with your gRPC server. Tyk provides pre-generated [bindings](https://github.com/TykTechnologies/tyk/tree/master/coprocess/bindings) for C++, Java, Python and Ruby.
 
-Example tutorials are available that explain how to generate the protobuf bindings and implement a server for [Java]({{< ref "api-management/plugins/rich-plugins#create-a-request-transformation-plugin-with-java" >}}), [.NET]({{< ref "api-management/plugins/rich-plugins#create-custom-authentication-plugin-with-net" >}}) and [NodeJS]({{< ref "api-management/plugins/rich-plugins#create-custom-authentication-plugin-with-net" >}}).
+Example tutorials are available that explain how to generate the protobuf bindings and implement a server for [Java]({{< ref "api-management/plugins/rich-plugins#create-a-request-transformation-plugin-with-java" >}}), [.NET]({{< ref "api-management/plugins/rich-plugins#create-custom-auth-plugin-with-dotnet" >}}) and [NodeJS]({{< ref "api-management/plugins/rich-plugins#create-custom-auth-plugin-with-dotnet" >}}).
 
 Tyk Github repositories are also available with examples for [Ruby](https://github.com/TykTechnologies/tyk-plugin-demo-ruby) and [C#/.NET](https://github.com/TykTechnologies/tyk-plugin-demo-dotnet)
 
@@ -1482,7 +1482,7 @@ This guide has explained the key concepts and processes for writing gRPC plugins
 #### What's Next?
 
 - Consult the [Protocol Buffer messages]({{< ref "api-management/plugins/rich-plugins#rich-plugins-data-structures" >}}) that Tyk Gateway uses when making a request to a gRPC server.
-- Visit tutorial guides that explain how to implement a [Java]({{< ref "api-management/plugins/rich-plugins#create-a-request-transformation-plugin-with-java" >}}), [.NET]({{< ref "api-management/plugins/rich-plugins#create-custom-authentication-plugin-with-net" >}}) and [NodeJS]({{< ref "api-management/plugins/rich-plugins#create-custom-authentication-plugin-with-net" >}}) gRPC server.
+- Visit tutorial guides that explain how to implement a [Java]({{< ref "api-management/plugins/rich-plugins#create-a-request-transformation-plugin-with-java" >}}), [.NET]({{< ref "api-management/plugins/rich-plugins#create-custom-auth-plugin-with-dotnet" >}}) and [NodeJS]({{< ref "api-management/plugins/rich-plugins#create-custom-auth-plugin-with-dotnet" >}}) gRPC server.
 - Visit our [plugins hub]({{< ref "api-management/plugins/overview#plugins-hub" >}}) to explore further gRPC development examples and resources.
 
 ---
@@ -2297,7 +2297,7 @@ To publish the plugin, copy or upload `bundle.zip` to a local web server like Ng
 
 {{< include "grpc-include" >}}
 
-#### <a name="next"></a>What's Next?
+#### What's Next? {what-is-next}
 
 In this tutorial we learned how Tyk gRPC plugins work. For a production-level setup we suggest the following:
 
@@ -2308,7 +2308,7 @@ In this tutorial we learned how Tyk gRPC plugins work. For a production-level se
 [3]: /img/dashboard/system-management/api_settings.png
 [4]: /img/dashboard/system-management/plugin_options.png
 
-### Create Custom Authentication Plugin with .NET
+### Create Custom Authentication Plugin with .NET {#create-custom-auth-plugin-with-dotnet}
 
 This tutorial will guide you through the creation of a custom authentication plugin for Tyk with a gRPC based plugin with .NET and C#. For additional information check the official gRPC [documentation](https://grpc.io/docs/guides/index.html).
 
@@ -2326,7 +2326,7 @@ The sample code that we’ll use implements a very simple authentication layer u
 
 #### Create the Plugin
 
-##### Create .NET Project
+##### Create .NET Project {#create-dotnet-project}
 
 We use the .NET CLI tool to generate the initial files for our project:
 
@@ -2349,7 +2349,7 @@ dotnet add package Google.Protobuf --version 3.4.0
 - The `ThreadPool` package is used by `Grpc`.
 - The `Protobuf` package will be used by our gRPC bindings.
 
-##### Install the gRPC Tools
+##### Install the gRPC Tools {#install-grpc-tools}
 
 We need to install the gRPC tools to generate the bindings. We recommended you follow the official guide here: https://grpc.io/docs/quickstart/csharp.html#generate-grpc-code.
 

tyk-docs/content/apim/open-source/installation.md

@@ -142,7 +142,7 @@ REDIS_BITNAMI_CHART_VERSION=19.0.2
 helm repo add tyk-helm https://helm.tyk.io/public/helm/charts/
 helm repo update
 
-helm upgrade tyk-redis oci://registry-1.docker.io/bitnamicharts/redis -n $NAMESPACE --install --version $REDIS_BITNAMI_CHART_VERSION
+helm upgrade tyk-redis oci://registry-1.docker.io/bitnamicharts/redis -n $NAMESPACE --create-namespace --install --version $REDIS_BITNAMI_CHART_VERSION
 
 helm upgrade tyk-oss tyk-helm/tyk-oss -n $NAMESPACE --create-namespace \
   --install \

tyk-docs/content/basic-config-and-security/security/authentication-authorization/multiple-auth.md

@@ -70,7 +70,7 @@ In the following example, the OpenAPI description includes multiple security sch
 }
 ```
 
-Tyk will consider only the first entry in the `security` list and so will implement the `auth-A` and `auth-B` schemes.
+Tyk will consider only the first entry in the `security` list and so will implement the `auth-A` and `auth-C` schemes.
 
 In the Tyk Vendor Extension this would result in the following configuration: