> For the complete documentation index, see [llms.txt](https://karedi.gitbook.io/karedi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://karedi.gitbook.io/karedi/user-interface/upper-components/lyrics-editor/line-breaks.md).
# Line breaks
As previously mentioned, lyrics editor only changes the way lyrics are distributed over the notes - the notes (visible in the [main editor](/karedi/user-interface/middle-components/main-editor.md)) are the primary source of data about the vocal track, lyrics are secondary to them.
You already know that the number of chunks in a line must match the number of notes in the same line. The same rule applies to the lines themselves - the number of lines into which the lyrics are split, must match the number of lines into which the notes are split.
Conceptually, when mapping vocal track you don't split lyrics into lines, but organize notes into lines (and later assign lyrics to them). Arguably the way these lyrics are sung matters more than the actual text when it comes to splitting into lines - the pauses the singer takes, how much time the note/line lasts etc.
Therefore to change the number of lines, you need to invoke the *toggle line break* action, which is originally main editor's action but it can also be invoked in the lyrics editor by using the `enter` key.
## Joining two lines
To join two lines together, you need to go to the first chunk of text in the latter line:
and press `enter` key:
## Splitting line into two
To split some line into two, you need to go to the chunk that should begin the new line:
and press `enter` key:
{% hint style="info" %}
As the "toggle line break" name suggests, if you invoke the action twice you will achieve the original state
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://karedi.gitbook.io/karedi/user-interface/upper-components/lyrics-editor/line-breaks.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.