fix readme

README.md

@@ -12,10 +12,10 @@ Danbooru 2023 datasets: https://huggingface.co/datasets/nyanko7/danbooru2023
 
 The latest entry of this database is id 7,866,491. Which is newer than nyanko7's dataset.
 
-This dataset contains a sqlite db file which have all the tags and posts metadata in it.`<br>`
+This dataset contains a sqlite db file which have all the tags and posts metadata in it.<br>
 The Peewee ORM config file is provided too, plz check it for more information. (Especially on how I link posts and tags together)
 
-The original data is from the official dump of the posts info.`<br>`
+The original data is from the official dump of the posts info.<br>
 Check this [link](https://console.cloud.google.com/storage/browser/danbooru_public/data) for more info.
 
 ## Format
@@ -54,8 +54,8 @@ Some fields in Post/Tags use my custom enum field to store type/category or some
 
 #### Tag List
 
-I use peewee ManyToManyField to implement the Tag List things. Which utilize a through model which have all the pair of Tag and Post`<br>`
-Since it is very likely we will want to use Tag to query posts, so many-to-many is better.`<br>`
+I use peewee ManyToManyField to implement the Tag List things. Which utilize a through model which have all the pair of Tag and Post<br>
+Since it is very likely we will want to use Tag to query posts, so many-to-many is better.<br>
 The con of this design is the database file will be 1.5x larger than before(we have 0.25B entries for the post-tag pairs), but the query speed become 2~3x faster, so I think it is acceptable.
 
 After done some checking, I can ensure that all the "categorical tag list" can be done by full list + filter, and that is how I done it now. Check the db.py for more details.