Merge Commit showing in Zip Readme

[jojo2357]

I really hope this isnt a style choice, but I noticed that in the readme in the root of the zip provided both here and on curseforge has what looks like a merge conflict in plaintext. it starts off

<<<<<<< HEAD

and ends

>>>>>>> d4d76b8ce1de19e4579f2547766a1503c735d086

which threw me for a loop because the whole file uses the ==== style of header instead of the # style of header.

This was in fact fixed in f5dd566 and should be updated accordingly, but I still see an issue on the line WaylandSmith ======= REPOSoftTech Utilities ======================

My markdown renderer as well as Github both use the LaTeX style of destroying newlines at will, and thus the REPOSoftTech Utilities does not show up as a header, but rather all on the same line. Moreover I do not see anyone in the contributor section with this name so I am led to believe it to be an error.

[HebaruSan]

That's how git handles conflicts. Normally you resolve them before committing.