Skip to content

Commit 44eef83

Browse files
authored
Update README.md
1 parent 95cec15 commit 44eef83

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -172,7 +172,7 @@ All this settings could be adjusted in the __#define__ statements at the beginni
172172

173173
This is because **AStar()** needs this 2-dimensional vector <br>
174174
to figure out wheather its a walkable or not walkable terrain. <br><br>
175-
**prepare_maze()** can handle a vector\<string> or vector\<vector\<char>> <br>
175+
**prepare_maze()** can handle a *vector\<string>* or *vector\<vector\<char>>* <br>
176176

177177
https://github.com/LukeProducts/AStar-Pathfinding-Cpp/blob/14c2a2b6773bd87094b09eae8189e36539831fc7/examples/prepare_maze.cpp#L7-L32
178178

@@ -197,7 +197,7 @@ what happens:
197197

198198

199199
**find_obj** finds an character out of a maze in ascii format, <br>
200-
such as vector\<string> or vector\<vector\<char>> <br>
200+
such as *vector\<string>* or *vector\<vector\<char>>* <br>
201201
and returns a vector\<int> with the (x, y) position of the character into the maze. <br><br>
202202
This is usefull to figure out the start and ends position in your maze, <br>
203203
so that you can pass this info into Astar(), which needs the position <br>

0 commit comments

Comments
 (0)