From 3242f9b97f9e9fdb55daf30de716b94ca59d19be Mon Sep 17 00:00:00 2001
From: Rafael Costa <80427734+raamcosta@users.noreply.github.com>
Date: Sun, 5 May 2024 11:30:22 +0100
Subject: [PATCH] Update README.md

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 1b5dac79..3edab0d7 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,6 @@
 # ⚠️ WARNING - `1.11.3-alpha` / `2.1.0-beta02` and above (Compose 1.7)
 
-## **DO NOT call `NavController.navigate` function** anywhere
+## - **DO NOT call `NavController.navigate` function** anywhere
 With the introduction of type safe APIs on the official library, our `NavController` extension functions that received `Direction` are now shadowed by new member functions on `NavController`.
 This means that the official member function would be called instead of our extension functions, and so we removed those extension functions.
 Instead, always make sure to use `DestinationsNavigator`. You can get one of such navigators by:
@@ -13,7 +13,7 @@ Instead, always make sure to use `DestinationsNavigator`. You can get one of suc
 
 Read more about these changes [here](https://github.com/raamcosta/compose-destinations/releases/tag/2.1.0-beta02).
 
-## **DO NOT depend on jetpack compose navigation directly**
+## - **DO NOT depend on jetpack compose navigation directly**
 Compose Destinations provides the correct version transitively.
 So, if you have dependency on `androidx.navigation:navigation-compose`, please remove it! This has always been true, but more important now.