minor fixes

Removing preview tag

first path of preview tag removal

Removed preview tag

Author: flang-msft

articles/redis/administration.md

@@ -1,5 +1,5 @@
 ---
-title: How to administer Azure Managed Redis (preview)
+title: How to administer Azure Managed Redis
 description: Learn how to perform administration tasks such as reboot and schedule updates for Azure Managed Redis
 
 ms.service: azure-managed-redis
@@ -10,9 +10,9 @@ ms.date: 11/15/2024
 appliesto:
   - ✅ Azure Managed Redis
 ---
-# How to administer Azure Managed Redis (preview)
+# How to administer Azure Managed Redis
 
-This article describes how to do administration tasks such as [rebooting](#reboot) and [Update channel and Schedule updates](#update-channel-and-schedule-updates) for your Azure Managed Redis (preview)instances.
+This article describes how to do administration tasks such as [rebooting](#reboot) and [Update channel and Schedule updates](#update-channel-and-schedule-updates) for your Azure Managed Redisinstances.
 
 ## Reboot
 

articles/redis/architecture.md

@@ -1,5 +1,5 @@
 ---
-title: Azure Managed Redis (preview) Architecture
+title: Azure Managed Redis Architecture
 description: Learn how Azure Managed Redis is architected
 
 ms.service: azure-managed-redis
@@ -11,9 +11,9 @@ appliesto:
   - ✅ Azure Managed Redis
 ---
 
-# Azure Managed Redis (preview) Architecture
+# Azure Managed Redis Architecture
 
-Azure Managed Redis (preview) runs on the [Redis Enterprise](https://redis.io/technology/advantages/) stack, which offers significant advantages over the community edition of Redis. The following information provides greater detail about how Azure Managed Redis is architected, including information that can be useful to power users.
+Azure Managed Redis runs on the [Redis Enterprise](https://redis.io/technology/advantages/) stack, which offers significant advantages over the community edition of Redis. The following information provides greater detail about how Azure Managed Redis is architected, including information that can be useful to power users.
 
 > [!IMPORTANT]
 > Azure Managed Redis is currently in PREVIEW.

articles/redis/aspnet-core-output-cache-provider.md

@@ -133,7 +133,7 @@ It's a security best practice to avoid storing passwords in clear text in source
 
     You can find the connection string for open source Redis tiers by selecting **Authentication** on the **Resource** menu. Here's an example string: `<Azure_redis_name>.redis.cache.windows.net:6380,password=<Azure_redis_primary_accesskey>,ssl=True,abortConnect=False`.
 
-    You can find the access keys for Redis Enterprise or Azure Managed Redis (Preview) by selecting **Access keys** on the **Resource** menu. The connection string can be derived with other Redis information from the **Overview** section of the **Resource** menu. Here's an example string: `<Azure_redis_name>.<Azure_region>.redisenterprise.cache.azure.net:10000,password=<Azure_redis_primary_accesskey>,ssl=True,abortConnect=False`.
+    You can find the access keys for Redis Enterprise or Azure Managed Redis by selecting **Access keys** on the **Resource** menu. The connection string can be derived with other Redis information from the **Overview** section of the **Resource** menu. Here's an example string: `<Azure_redis_name>.<Azure_region>.redisenterprise.cache.azure.net:10000,password=<Azure_redis_primary_accesskey>,ssl=True,abortConnect=False`.
 
 1. Set the Redis connection for the web application by using the Azure CLI:
 

articles/redis/aspnet-output-cache-provider.md

@@ -55,7 +55,7 @@ Configure the attributes in the first column with the values from your cache in
 | Attribute | Type | Default | Description |
 | --------- | ---- | ------- | ----------- |
 | _host* | string | "localhost" | The Redis server IP address or host name |
-| _port_ | positive integer | 6379 (non-TLS/SSL)<br/>6380 (TLS/SSL)<br/>10000 for Redis Enterprise and Azure Managed Redis (Preview) | Redis server port |
+| _port_ | positive integer | 6379 (non-TLS/SSL)<br/>6380 (TLS/SSL)<br/>10000 for Redis Enterprise and Azure Managed Redis | Redis server port |
 | _accessKey_ | string | "" | Redis server password when Redis authorization is enabled. The value is an empty string by default, which means the session state provider doesn't use any password when it connects to Redis server. **If your Redis server is in a publicly accessible network like Azure Cache for Redis, be sure to enable Redis authorization to improve security, and provide a secure password.** |
 | _ssl_ | boolean | **false** | Whether to connect to Redis server via TLS. This value is **false** by default because Redis doesn’t support TLS by default. **If you're using Azure Cache for Redis, which supports SSL by default, be sure to set this value to true to improve security.**<br/><br/>The non-TLS port is disabled by default for new caches. Specify **true** for this setting to use the non-TLS port. For more information about enabling the non-TLS port, see the [Access Ports](configure.md#access-ports) section in the [Configure a cache](configure.md) article. |
 | _databaseIdNumber_ | positive integer | 0 | _This attribute can be specified only through either web.config or AppSettings._<br/><br/>Specify which Redis database to use. |

articles/redis/best-practices-client-libraries.md

@@ -1,5 +1,5 @@
 ---
-title: Best practices using client libraries with Azure Managed Redis (preview)
+title: Best practices using client libraries with Azure Managed Redis
 description: Learn about client libraries for Azure Managed Redis.
 
 ms.service: azure-managed-redis
@@ -10,9 +10,9 @@ appliesto:
   - ✅ Azure Managed Redis
 ---
 
-# Azure Managed Redis (preview) Client libraries
+# Azure Managed Redis Client libraries
 
-Azure Managed Redis (preview) is based on the popular in-memory data store, Redis. Redis clients for many programming languages can access Azure Managed Redis. Each client library has its own API that makes calls to Redis server using Redis commands, but the client libraries are built to talk to any Redis server.
+Azure Managed Redis is based on the popular in-memory data store, Redis. Redis clients for many programming languages can access Azure Managed Redis. Each client library has its own API that makes calls to Redis server using Redis commands, but the client libraries are built to talk to any Redis server.
 
 Each client library maintains its own reference documentation. The libraries also provide links to get support through the client library developer community. The Azure Managed Redis team doesn't own the development, or the support for any client libraries.
 

articles/redis/best-practices-connection.md

@@ -11,7 +11,7 @@ appliesto:
   - ✅ Azure Managed Redis
 ---
 
-# Connection resilience with Azure Managed Redis (preview)
+# Connection resilience with Azure Managed Redis
 
 ## Retry commands
 
@@ -86,7 +86,7 @@ Apply design patterns for resiliency. For more information, see [How do I make m
 
 ## Idle timeout
 
-Azure Managed Redis (preview) has a 10-minute timeout for idle connections. The 10-minute timeout allows the server to automatically clean up leaky connections or connections orphaned by a client application. Most Redis client libraries have a built-in capability to send `heartbeat` or `keepalive` commands periodically to prevent connections from being closed even if there are no requests from the client application.
+Azure Managed Redis has a 10-minute timeout for idle connections. The 10-minute timeout allows the server to automatically clean up leaky connections or connections orphaned by a client application. Most Redis client libraries have a built-in capability to send `heartbeat` or `keepalive` commands periodically to prevent connections from being closed even if there are no requests from the client application.
 
 If there's any risk of your connections being idle for 10 minutes, configure the `keepalive` interval to a value less than 10 minutes. If your application is using a client library that doesn't have native support for `keepalive` functionality, you can implement it in your application by periodically sending a `PING` command.
 

articles/redis/best-practices-development.md

@@ -1,5 +1,5 @@
 ---
-title: Best practices for development for Azure Managed Redis (preview)
+title: Best practices for development for Azure Managed Redis
 description: Learn how to develop code for Azure Managed Redis.
 
 ms.service: azure-managed-redis
@@ -19,7 +19,7 @@ When developing client applications, be sure to consider the relevant best pract
 
 ## Consider more keys and smaller values
 
-Azure Managed Redis (preview) works best with smaller values. To spread the data over multiple keys, consider dividing bigger chunks of data in to smaller chunks. For more information on ideal value size, see this [article](https://stackoverflow.com/questions/55517224/what-is-the-ideal-value-size-range-for-redis-is-100kb-too-large/).
+Azure Managed Redis works best with smaller values. To spread the data over multiple keys, consider dividing bigger chunks of data in to smaller chunks. For more information on ideal value size, see this [article](https://stackoverflow.com/questions/55517224/what-is-the-ideal-value-size-range-for-redis-is-100kb-too-large/).
 
 ## Large request or response size
 

articles/redis/best-practices-kubernetes.md

@@ -1,5 +1,5 @@
 ---
-title: Best practices for hosting a Kubernetes client application for Azure Managed Redis (preview)
+title: Best practices for hosting a Kubernetes client application for Azure Managed Redis
 description: Learn how to host a Kubernetes client application that uses Azure Managed Redis.
 
 ms.service: azure-managed-redis
@@ -10,7 +10,7 @@ appliesto:
   - ✅ Azure Managed Redis
 ---
 
-# Kubernetes-hosted client application with Azure Managed Redis (preview)
+# Kubernetes-hosted client application with Azure Managed Redis
 
 ## Client connections from multiple pods
 
@@ -28,7 +28,7 @@ A pod running the client application can be affected by other pods running on th
 
 ## Linux-hosted client applications and TCP settings
 
-If your Azure Managed Redis (preview) client application runs on a Linux-based container, we recommend updating some TCP settings. These settings are detailed in [TCP settings for Linux-hosted client applications](best-practices-connection.md#tcp-settings-for-linux-hosted-client-applications).
+If your Azure Managed Redis client application runs on a Linux-based container, we recommend updating some TCP settings. These settings are detailed in [TCP settings for Linux-hosted client applications](best-practices-connection.md#tcp-settings-for-linux-hosted-client-applications).
 
 ## Related content
 

articles/redis/best-practices-managed-cache.md

@@ -11,9 +11,9 @@ appliesto:
   - ✅ Azure Managed Redis
 ---
 
-# What are the best practices for the Azure Managed Redis (preview)
+# What are the best practices for the Azure Managed Redis
 
-Here are some best practices for Azure Managed Redis (preview).
+Here are some best practices for Azure Managed Redis.
 
 ## Zone redundancy
 

articles/redis/best-practices-memory-management.md

@@ -1,5 +1,5 @@
 ---
-title: Best practices for memory management for Azure Managed Redis (preview)
+title: Best practices for memory management for Azure Managed Redis
 description: Learn how to manage your Azure Managed Redis memory effectively with Azure Managed Redis.
 
 ms.service: azure-managed-redis
@@ -11,11 +11,11 @@ appliesto:
   - ✅ Azure Managed Redis
 ---
 
-# Memory management for Azure Managed Redis (preview)
+# Memory management for Azure Managed Redis
 
 ## Eviction policy
 
-Choose an [eviction policy](https://redis.io/topics/lru-cache)that works for your application. The default policy for Azure Managed Redis (preview) is `volatile-lru`, which means that only keys that have a TTL value set with a command like [EXPIRE](https://redis.io/commands/expire) are eligible for eviction.  If no keys have a TTL value, then the system won't evict any keys.  If you want the system to allow any key to be evicted if under memory pressure, then you may want to consider the `allkeys-lru` policy.
+Choose an [eviction policy](https://redis.io/topics/lru-cache)that works for your application. The default policy for Azure Managed Redis is `volatile-lru`, which means that only keys that have a TTL value set with a command like [EXPIRE](https://redis.io/commands/expire) are eligible for eviction.  If no keys have a TTL value, then the system won't evict any keys.  If you want the system to allow any key to be evicted if under memory pressure, then you may want to consider the `allkeys-lru` policy.
 
 ## Keys expiration