Merge pull request #26993 from MicrosoftDocs/main

05/05 PM Publishing

Author: v-alje

azure-sql/database/high-availability-sla.md

@@ -103,7 +103,7 @@ For more information on high availability in Hyperscale, see [Database High Avai
 
 ## Zone-redundant availability 
 
-Zone-redundant availability is based on storing your database to [zone-redundant storage (ZRS)](/azure/storage/common/storage-redundancy#zone-redundant-storage), which copies your data across three Azure availability zones in the primary region. Each availability zone is a separate physical location with independent power, cooling, and networking. Each availability zone is a separate physical location with independent power, cooling, and networking.
+Zone-redundant availability is based on storing your database to [zone-redundant storage (ZRS)](/azure/storage/common/storage-redundancy#zone-redundant-storage), which copies your data across three Azure availability zones in the primary region. Each availability zone is a separate physical location with independent power, cooling, and networking.
 
 Zone-redundant availability is available to databases in the General Purpose, Premium, Business Critical and Hyperscale service tiers of the vCore purchasing model, and not the Basic and Standard service tiers of the DTU-based purchasing model. 
 

docs/connect/jdbc/codesnippet/Java/handling-errors_1.java

@@ -13,7 +13,6 @@ public static void executeSQLException(Connection con) {
             System.out.println("ERROR CODE: " + se.getErrorCode());
             System.out.println("MESSAGE: " + se.getMessage());
             System.out.println();
-            se = se.getNextException();
         }
         while (se != null);
     }