@codebrainz approved this pull request.

I like these changes, just the list nesting comment I think is an actual problem.

> @@ -3042,16 +3039,16 @@ behaviors:
   compiler tab and parse it for errors.
 * Execute commands - are configurable and intended for executing your
   program or other long running programs.  The output is not parsed for errors
-  and is directed to the terminal command selected in preferences.
+  and is directed to the terminal command selected in *Preferences*.

Alternative for *Preferences* could be `Tools preferences`_.

In doc/geany.txt:

>  * Fixed commands - these perform built-in actions:
 
-  * Go to the next error.
-  * Go to the previous error.
-  * Show the build menu commands dialog.
+* Go to the next error.
+* Go to the previous error.
+* Show the build menu commands dialog.

I think this indentation was intentional for nesting.

In doc/geany.txt:

>    execute and preferences independent execute commands can only be set by hand
   editing the appropriate file, see `Preferences file format`_ and `Project file
   format`_.
 
-Build menu commands dialog
-^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Most of the configuration of the build menu is done through the Build Menu
-Commands Dialog.  You edit the configuration sourced from preferences in the
-dialog opened from the Build->Build Menu Commands item and you edit the
-configuration from the project in the build tab of the project preferences
-dialog.  Both use the same form shown below.
+Set Build Commands dialog
+^^^^^^^^^^^^^^^^^^^^^^^^^
+ 
+Most of the configuration of the build menu is done through the *Set 
+Build Commands* dialog. When no project is open, you can edit the

Could use `Set Build Commands dialog`_ or whatever is the hyperlink syntax.

In doc/geany.txt:

>  An item with an empty label will not be shown in the menu.
-

If merging into a single paragraph, a reflow of the new paragraph might be in order, not a big deal though.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.