HeySummit uses rich-text controls in many content areas, while some fields still accept Markdown or plain text. Start by checking which editor is shown for the field that looks wrong.
Match the fix to the editor
Rich-text editor: use the editor toolbar for headings, emphasis, lists, and links. If text copied from another document brings unwanted styling, remove its formatting or paste it as plain text, then apply the formatting again in HeySummit.
Markdown or plain-text field: characters at the start of a line can change the result. For example, a leading # can create a heading and asterisks can create emphasis. Use a backslash before a Markdown character when you need to display it literally, such as \#topic.
Custom CSS: event-level CSS can change how otherwise correct text appears on public pages. Test the affected page without the relevant custom rule before changing the article text itself.
Preview and isolate the problem
Save the field and preview the exact public page or email where it appears.
Test a short plain-text version in the same field. If that looks correct, add the intended formatting back one change at a time.
If the problem remains, contact HeySummit support with the event page URL, the field or editor name, a short example of the text you entered, and a screenshot of the result. Do not include private attendee data.