From 4f871d8dc57f71cd290c893b5df770242e8a8226 Mon Sep 17 00:00:00 2001
From: Jonathan Michaux <5730842+jmcx@users.noreply.github.com>
Date: Tue, 21 Nov 2023 17:38:02 +0100
Subject: [PATCH] Add "push" plans to plans overview

fixed https://github.com/gravitee-io/gravitee-platform-docs/issues/65
---
 .../README.md                                                  | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/docs/apim/4.1/guides/api-exposure-plans-applications-and-subscriptions/README.md b/docs/apim/4.1/guides/api-exposure-plans-applications-and-subscriptions/README.md
index 2cced11f2..69d992647 100644
--- a/docs/apim/4.1/guides/api-exposure-plans-applications-and-subscriptions/README.md
+++ b/docs/apim/4.1/guides/api-exposure-plans-applications-and-subscriptions/README.md
@@ -14,12 +14,13 @@ There are many possible types of API access scenarios, which can be difficult to
 
 A plan provides a service and access layer on top of your APIs for consumer applications. A plan specifies access limits, subscription validation modes, and other configurations to tailor it to a specific application.
 
-The most important part of plan configuration is selecting the security type. APIM supports the following four security types:
+The most important part of plan configuration is selecting the security type. APIM supports the following five security types:
 
 * Keyless (public)
 * API Key
 * OAuth 2.0
 * JWT
+* Push
 
 Exposing an API to a consumer requires at least one plan, but can support as many plans as needed. These are just some sample access scenarios APIM can manage with plans: