From 44eef83aaef6b7a4414e1bfd9801a07eb7c8ae52 Mon Sep 17 00:00:00 2001
From: LukeProducts <lukas_zander@gmx.net>
Date: Fri, 11 Mar 2022 17:06:20 +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 303e7f9..6430fe4 100644
--- a/README.md
+++ b/README.md
@@ -172,7 +172,7 @@ All this settings could be adjusted in the __#define__ statements at the beginni
 
 This is because **AStar()** needs this 2-dimensional vector <br>
 to figure out wheather its a walkable or not walkable terrain. <br><br>
-**prepare_maze()** can handle a vector\<string> or vector\<vector\<char>> <br>
+**prepare_maze()** can handle a *vector\<string>* or *vector\<vector\<char>>* <br>
  
 https://github.com/LukeProducts/AStar-Pathfinding-Cpp/blob/14c2a2b6773bd87094b09eae8189e36539831fc7/examples/prepare_maze.cpp#L7-L32
 
@@ -197,7 +197,7 @@ what happens:
  
  
  **find_obj** finds an character out of a maze in ascii format, <br>
- such as vector\<string> or vector\<vector\<char>> <br>
+ such as *vector\<string>* or *vector\<vector\<char>>* <br>
  and returns a vector\<int> with the (x, y) position of the character into the maze. <br><br>
  This is usefull to figure out the start and ends position in your maze, <br>
  so that you can pass this info into Astar(), which needs the position <br>