# \[x\] - mark down putting in a line break

**URL:** <https://community.noloco.io/t/x-mark-down-putting-in-a-line-break/261>\
**Category:** Bugs\
**Created:** [February 13, 2024, 8:36am UTC](https://community.noloco.io/t/x-mark-down-putting-in-a-line-break/261 "2024-02-13T08:36:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kieran](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/kieran/32/91_2.png) [@Kieran](https://community.noloco.io/u/Kieran)\
**Post date:** [February 13, 2024, 8:36am UTC](https://community.noloco.io/t/x-mark-down-putting-in-a-line-break/261/1 "2024-02-13T08:36:32Z")

</div>

When using the mark down to get a nice check box (I am using it as some feedback in the UI when a call to chat gpt has changed a field) unfortunately after the check box there is an unwanted line break after the check box and the text.

So it looks like

The field has been updated

---

<div class="post-metadata">

**Author:** ![darragh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/darragh/32/12_2.png) [@darragh](https://community.noloco.io/u/darragh)\
**Post date:** [February 13, 2024, 9:59am UTC](https://community.noloco.io/t/x-mark-down-putting-in-a-line-break/261/2 "2024-02-13T09:59:58Z")

</div>

Hi @Kieran - would you be able to share a screenshot of this in the app, and ideally a link to the page it’s happening on so we can double check what’s happening

---

<div class="post-metadata">

**Author:** ![Kieran](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/kieran/32/91_2.png) [@Kieran](https://community.noloco.io/u/Kieran)\
**Post date:** [February 13, 2024, 1:40pm UTC](https://community.noloco.io/t/x-mark-down-putting-in-a-line-break/261/3 "2024-02-13T13:40:24Z")

</div>

Hey @darragh Yes of course.

[https://alet-marketing.noloco.co/partner-activity-posts/view/reckgdTzoFX6SokYk](https://alet-marketing.noloco.co/partner-activity-posts/view/reckgdTzoFX6SokYk)

Its the post schedule part (I have is on a conditional visibility but it was the same for both visible and not so I don’t think that is the cause.)

 ![Screenshot 2024-02-13 at 13.38.39](https://europe1.discourse-cdn.com/flex005/uploads/noloco/original/1X/ab1dc59f16c3cc1b6af668984fdf4174d7fecb23.png)