remove bogus information

Author: flang-msft

articles/redis/TOC.yml

@@ -22,7 +22,7 @@ items:
         href: how-to-manage-redis-cache-powershell.md
       - name: Create and manage with Azure CLI
         href: scripts/create-manage-cache.md
-      - name: Create and manage premium cache with Azure CLI
+      - name: Create and manage a premium cache with Azure CLI
         href: ../azure-cache-for-redis/scripts/create-manage-premium-cache-cluster.md
       - name: Create Redis cache - Bicep
         displayName: ARM, Resource Manager, Template
@@ -67,8 +67,6 @@ items:
       href: how-to-upgrade.md
     - name: Save with reservations 
       href: reserved-pricing.md
-    - name: Migrate to Azure Redis from other caches
-      href: /migrate/migration-guide.md
     - name: Planning FAQs
       href: planning-faq.yml
     - name: Redis modules 
@@ -171,12 +169,8 @@ items:
       href: how-to-persistence.md
     - name: Set up Enterprise active geo-replication
       href: how-to-active-geo-replication.md
-    - name: Configure your cache for high availability
-      href: high-availability.md
     - name: Failover and patching
       href: failover.md
-    - name: Migrate to availability zone support
-      href: ../reliability/migrate-cache-redis.md
 
   - name: Diagnose and troubleshoot
     items:

articles/redis/how-to-manage-redis-cache-powershell.md

@@ -535,4 +535,3 @@ For more information about Microsoft Azure Germany, see [Microsoft Azure Germany
 * [Azure Cache for Redis cmdlets](/powershell/module/az.rediscache)
 * [Azure PowerShell cmdlets](/powershell/module/)
 * [PowerShell Community blog](https://devblogs.microsoft.com/powershell-community/)
-

articles/redis/migrate/migration-guide.md

@@ -61,8 +61,7 @@ Open-source Redis defines a standard mechanism for taking a snapshot of a cache'
 
 General steps to implement this option are:
 
-<!-- cawa - remove reference to premium tier -->
-1. Create a new Azure Managed Redis instance in the premium tier that is the same size as (or bigger than) the existing cache.
+1. Create a new Azure Managed Redis instance i that is the same size as (or bigger than) the existing cache.
 
 2. Save a snapshot of the existing Redis cache. You can [configure Redis to save snapshots](https://redis.io/topics/persistence) periodically, or run the process manually using the [SAVE](https://redis.io/commands/save) or [BGSAVE](https://redis.io/commands/bgsave) commands. The RDB file is named “dump.rdb” by default and will be located at the path specified in the *redis.conf* configuration file.
 
@@ -82,7 +81,7 @@ Rather than moving data directly between caches, you may use your application to
 
 General steps to implement this option are:
 
-1. Create a new Azure Managed Redis instance in the premium tier that is the same size as (or bigger than) the existing cache.
+1. Create a new Azure Managed Redis instance that is the same size as (or bigger than) the existing cache.
 
 2. Modify application code to write to both the new and the original instances.