Merge branch 'richagaur/understanding-ru-consumption' of https://github.com/richagaur/azure-databases-docs-pr into richagaur/understanding-ru-consumption

Author: richagaur

articles/cosmos-db/TOC.yml

@@ -316,7 +316,7 @@
     - name: Best practices for scaling provisioned throughput
       href: scaling-provisioned-throughput-best-practices.md?context=/azure/cosmos-db/context/context
     - name: Understanding request unit consumption
-      href: understand-ru-consumption.md?context=/azure/cosmos-db/context/context
+      href: understand-request-unit-consumption.md?context=/azure/cosmos-db/context/context
     - name: Burst capacity
       items:
         - name: Burst capacity overview

…s/cosmos-db/understand-ru-consumption.md …b/understand-request-unit-consumption.mdarticles/cosmos-db/understand-ru-consumption.md renamed to articles/cosmos-db/understand-request-unit-consumption.md articles/cosmos-db/understand-ru-consumption.md renamed to articles/cosmos-db/understand-request-unit-consumption.md

@@ -77,7 +77,8 @@ Although specific RU values can change over time, the principles remain consiste
 
 Request units are consumed based on the work required to perform an operation. This section explains how RUs are consumed across common document operations, using illustrative examples to highlight the underlying principles.
 
-> [!Important]
+
+> [!IMPORTANT]
 > The RU values described in this document are illustrative and reflect how Azure Cosmos DB processes operations at a given point in time.
 
 ### Write Operations