Remove false items

tyk-docs/content/api-management/automations/operator.md

@@ -257,7 +257,7 @@ To address this challenge, Tyk Operator allows you to directly reference certifi
 
 We assume you have already installed Tyk. If you don’t have it, check out [Tyk
 Cloud]({{< ref "tyk-cloud#quick-start-tyk-cloud" >}}) or [Tyk Self
-Managed]({{< ref "getting-started/installation" >}}) page. [Tyk Helm
+Managed]({{< ref "tyk-self-managed" >}}) page. [Tyk Helm
 Chart]({{< ref "product-stack/tyk-charts/overview" >}}) is the preferred (and easiest) way to install Tyk on Kubernetes.
 
 In order for policy ID matching to work correctly, Dashboard must have `allow_explicit_policy_id` and

tyk-docs/content/api-management/dashboard-configuration.md

@@ -38,6 +38,8 @@ aliases:
   - /tyk-apis/tyk-dashboard-admin-api/import
   - /advanced-configuration/transform-traffic/endpoint-designer
   - /transform-traffic/endpoint-designer
+  - /tyk-dashboard/getting-started
+  - /basic-config-and-security/security/dashboard
 ## Traffic Analytics
   - /analyse
   - /tyk-stack/tyk-pump/tyk-dash-analytics

tyk-docs/content/api-management/gateway-config-introduction.md

@@ -8,6 +8,7 @@ aliases:
   - /getting-started/key-concepts/what-is-an-api-definition
   - /concepts/gateway-api
   - /getting-started/key-concepts/gateway-api
+  - /basic-config-and-security/security/gateway
   - /getting-started/key-concepts
 ---
 

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

@@ -555,7 +555,7 @@ curl -H "x-tyk-authorization: <secured-endpoint-secret>" https://my-mdcb-host:81
 
 Before a worker gateway can connect to MDCB, it is important to enable the organization that owns all the APIs to be distributed to be allowed to utilize Tyk MDCB. To do this, the organization record needs to be modified with two flags using the [Tyk Dashboard Admin API]({{< ref "dashboard-admin-api" >}}).
 
-To make things easier, we will first set a few [environment variables]({{< ref "tyk-environment-variables" >}}):
+To make things easier, we will first set a few [environment variables]({{< ref "tyk-oss-gateway/configuration" >}}):
 
 1. `export DASH_ADMIN_SECRET=<YOUR_ADMIN_SECRET>`
 

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

@@ -23,6 +23,7 @@ aliases:
   - /basic-config-and-security/control-limit-traffic/key-expiry
   - /basic-config-and-security/security/key-hashing
   - /basic-config-and-security/security/key-level-security
+  - /basic-config-and-security
   - /tyk-apis/tyk-gateway-api/token-session-object-details
 ---
 

tyk-docs/content/api-management/security-best-practices.md

@@ -115,7 +115,7 @@ Tyk offers several mechanisms to help protect an API from Security Misconfigurat
 - [Error Templates]({{< ref "api-management/gateway-events#error-templates" >}}) can be used to return a response body based on status code and content type. This can help minimize the implementation details returned to the client.
 - [CORS functionality]({{< ref "api-management/gateway-config-tyk-classic#cross-origin-resource-sharing-cors" >}}) allows the Tyk Gateway to limit API access to particular browser-based consumers.
 - [Policy Path-Based Permissions]({{< ref "api-management/policies#secure-your-apis-by-method-and-path" >}}) and the [allowlist]({{< ref "api-management/traffic-transformation#api-definition" >}}) plugin can be used to prevent clients from accessing API endpoints using non-authorized HTTP methods. For example, blocking the use of the DELETE method on an endpoint which should only accept GET requests.
-- [Environment variables]({{< ref "tyk-environment-variables" >}}) can help standardize configuration across containerised deployments.
+- [Environment variables]({{< ref "tyk-oss-gateway/configuration" >}}) can help standardize configuration across containerised deployments.
 - For GraphQL APIs:
 - [Schema Introspection]({{< ref "api-management/graphql#introspection" >}}) ensures that the Tyk Dashboard automatically uses the schema of the upstream GraphQL API and can keep it synchronised if it changes.
 - [GraphQL Schema Validation]({{< ref "api-management/graphql#schema-validation" >}}) prevents invalid schemas from being saved. This catches errors such as duplicate type names and usage of unknown types.

tyk-docs/content/api-management/traffic-transformation.md

@@ -68,6 +68,7 @@ aliases:
   - /advanced-configuration/transform-traffic/request-headers
   - /advanced-configuration/transform-traffic/request-body
   - /transform-traffic/endpoint-designer
+  - /advanced-configuration
 ---
 
 ## Overview

tyk-docs/content/api-management/troubleshooting-debugging.md

@@ -57,18 +57,20 @@ aliases:
     - /troubleshooting/tyk-pump/pump-overloaded
     - /tyk-configuration-reference/hot-restart-tyk-gateway-process
     - /tyk-stack/tyk-pump/useful-debug-modes
-    - analytics-and-reporting/useful-debug-modes
-    - debugging-series
-    - troubleshooting/tyk-cloud
-    - troubleshooting/tyk-dashboard
+    - /analytics-and-reporting/useful-debug-modes
+    - /debugging-series
+    - /troubleshooting/tyk-cloud
+    - /troubleshooting/tyk-dashboard
     - /troubleshooting/tyk-dashboard/fatal-dashboard-port...
-    - troubleshooting/tyk-gateway
-    - troubleshooting/tyk-installation
-    - troubleshooting/tyk-multi-cloud
-    - troubleshooting/tyk-pump
-    - tyk-rest-api/hot-reload
-    - tyk-stack/tyk-pump/tyk-pump-configuration/graceful-shutdowm
-    - frequently-asked-questions/add-custom-certificates-to-docker-images
+    - /troubleshooting/tyk-gateway
+    - /troubleshooting/tyk-installation
+    - /troubleshooting/tyk-multi-cloud
+    - /troubleshooting/tyk-pump
+    - /tyk-rest-api/hot-reload
+    - /tyk-stack/tyk-pump/tyk-pump-configuration/graceful-shutdowm
+    - /frequently-asked-questions/add-custom-certificates-to-docker-images
+    - /troubleshooting/tyk-on-premise/tyk-on-premise
+    - /troubleshooting/tyk-installation/parsing-json-error-from-dashboard-bootstrap
 ---
 
 ## Gateway