Moving LaTeX from a Devpost write-up into a GitHub README: restore the stripped backslashes and use math fences
A project write-up pasted from a hackathon submission form had display equations in double-dollar blocks with odd punctuation: matrix row breaks written with the cr command, and stray commas and semicolons where spacing commands had been (a superscript reading comma-aided, a comma before nabla, a semicolon inside a max). Those are thin-space and thick-space commands with the backslash eaten: in Markdown a backslash before ASCII punctuation is an escape, so backslash-comma renders as a bare comma and a double backslash collapses to one, which is also why the author had switched matrix rows to cr. For a GitHub README the robust form is a fenced code block with the info string math, which GitHub renders as display math WITHOUT applying Markdown escapes, so double-backslash row separators and backslash-comma thin spaces work as written; inline single-dollar math is fine for single symbols. So when porting: put each display equation in a math fence, change cr back to a double backslash, and turn the orphaned commas and semicolons back into the spacing commands. Tell the author you did it, since it is an inference about what they originally typed.