From 118fbe83be4d13bcc4bb33552e8eed3963a7183f Mon Sep 17 00:00:00 2001
From: Tharanidk <tharani.dayadhi@gmail.com>
Date: Tue, 5 Nov 2024 14:54:17 +0530
Subject: [PATCH] fix Review Changes

---
 .../design/create-api/adding-custom-properties-to-apis.md   | 5 -----
 .../design/rate-limiting/adding-new-throttling-policies.md  | 6 ++++--
 2 files changed, 4 insertions(+), 7 deletions(-)

diff --git a/en/docs/design/create-api/adding-custom-properties-to-apis.md b/en/docs/design/create-api/adding-custom-properties-to-apis.md
index 674361adc5..8dd07156dc 100644
--- a/en/docs/design/create-api/adding-custom-properties-to-apis.md
+++ b/en/docs/design/create-api/adding-custom-properties-to-apis.md
@@ -69,8 +69,3 @@ When you click on the name of the API in the above screen, the respective API Ov
 
 [![API Properties]({{base_path}}/assets/img/learn/view-custom-api-properties.png)]({{base_path}}/assets/img/learn/view-custom-api-properties.png)
 
-??? note "Note"
-        When devportal visibility is enabled for a property when searching from Publisher, we need to search it in the following manner.
-        <property_name>__display:<property_value>
-
-        For example, if you added a property called env with value dev, we need to search it in the publisher as env__display:dev.
\ No newline at end of file
diff --git a/en/docs/design/rate-limiting/adding-new-throttling-policies.md b/en/docs/design/rate-limiting/adding-new-throttling-policies.md
index 899f9e9649..65f97ec6bf 100644
--- a/en/docs/design/rate-limiting/adding-new-throttling-policies.md
+++ b/en/docs/design/rate-limiting/adding-new-throttling-policies.md
@@ -43,8 +43,10 @@ You can add advanced rate limiting policies to both APIs and resources.
      <li>
      Note that if you want to add a header, query param, or JSON Web Token (JWT) claim condition, you need to set the `enable_header_based_throttling` , `enable_jwt_claim_based_throttling` or `enable_query_param_based_throttling` element to `true` (depending on which condition you need) under `[apim.throttling]` in the `repository/conf/deployment.toml` file.</li>
       ```toml
-      [transport.passthru_https.sender.parameters]
-      HostnameVerifier = "AllowAll"
+      [apim.throttling]
+      enable_header_based_throttling = true
+      enable_jwt_claim_based_throttling = true
+      enable_query_param_based_throttling = true
       ```
      <li>This JWT is the backend JWT and not the one you use to invoke it. In addition, you need to enable the Backend JWT token to get this rate limiting flow to work.
      </li></ul>