Doc page with unescaped hashtags - math mode vs. code

Nobody has claimed this yet.

The doc page for higherHomotopies is currently broken because of unescaped hashtags. In particular, line 63 of the html code (view page source on the website, or 3715 in CompleteIntersectionResolutions.m2, read

```
... and $$ H#\{e0,i+1\}*H#\{e,i\}+H#\{e,i-1\}H#\{e0,i\} = f_i, $$ where $e0 = \{0,\dots,0\}$ and $e$...
```

but should be

```
... and $$ H\#\{e0,i+1\}*H\#\{e,i\}+H\#\{e,i-1\}H#\{e0,i\} = f_i, $$ where $e0 = \{0,\dots,0\}$ and $e$...
```

There are a number of other issues with the appearance of this documentation page. This is likely a more general problem affecting many pages.

More generally though, why are these being rendered as tex instead of as macaulay2 code, like in the following?

```

i1 : kk=ZZ/101


o1 = kk

o1 : QuotientRing

Start with line 3715 in CompleteIntersectionResolutions.m2 and compare it with line 63 of the generated HTML/source for the higherHomotopies page. Inspect how hashtags and Macaulay2 code blocks are rendered, then check whether the same issue appears on other documentation pages. Done means the affected page displays the intended math and code formatting, with the broader rendering behavior understood or corrected.

Written by the indexing model from the issue text.