Consistent capitalization of usage guide section names

doc/fluidsynth-v20-devdoc.txt

@@ -189,9 +189,9 @@ FluidSynths major version was bumped. The API was reworked, deprecated functions
 \page UsageGuide Usage Guide
  - \subpage CreatingSettings
  - \subpage CreatingSynth
+ - \subpage LoadingSoundfonts
  - \subpage CreatingAudioDriver
  - \subpage UsingSynth
- - \subpage LoadingSoundfonts
  - \subpage SendingMIDI
  - \subpage RealtimeMIDI
  - \subpage MIDIPlayer
@@ -252,7 +252,7 @@ For a full list of available <strong>synthesizer settings</strong>, please refer
 
 
 
-\page CreatingAudioDriver Creating the Audio Driver
+\page CreatingAudioDriver Creating the audio driver
 
 The synthesizer itself does not write any audio to the audio output. This allows application developers to manage the audio output themselves if they wish. The next section describes the use of the synthesizer without an audio driver in more detail.
 
@@ -319,7 +319,7 @@ The fluid_synth_sfload() function returns the unique identifier of the loaded So
 
 Additional API functions are provided to get the number of loaded SoundFonts and to get a pointer to the SoundFont. 
 
-\page SendingMIDI Sending MIDI Events
+\page SendingMIDI Sending MIDI events
 
 Once the synthesizer is up and running and a SoundFont is loaded, most people will want to do something useful with it. Make noise, for example. MIDI messages can be sent using the fluid_synth_noteon(), fluid_synth_noteoff(), fluid_synth_cc(), fluid_synth_pitch_bend(), fluid_synth_pitch_wheel_sens(), and fluid_synth_program_change() functions. For convenience, there's also a fluid_synth_bank_select() function (the bank select message is normally sent using a control change message). 
 
@@ -362,7 +362,7 @@ protected:
 };
 \endcode
 
-\page RealtimeMIDI Creating a Real-time MIDI Driver
+\page RealtimeMIDI Creating a real-time MIDI driver
 
 FluidSynth can process real-time MIDI events received from hardware MIDI ports or other applications. To do so, the client must create a MIDI input driver. It is a very similar process to the creation of the audio driver: you initialize some properties in a settings instance and call the new_fluid_midi_driver() function providing a callback function that will be invoked when a MIDI event is received. The following MIDI drivers are currently supported:
 
@@ -400,7 +400,7 @@ the MIDI subsystems used. For a full list of available <strong>midi driver setti
 
 
 
-\page MIDIPlayer Loading and Playing a MIDI file
+\page MIDIPlayer Loading and playing a MIDI file
 
 FluidSynth can be used to play MIDI files, using the MIDI File Player interface. It follows a high level implementation, though its implementation is currently incomplete. After initializing the synthesizer, create the player passing the synth instance to new_fluid_player(). Then, you can add some SMF file names to the player using fluid_player_add(), and finally call fluid_player_play() to start the playback. You can check if the player has finished by calling fluid_player_get_status(), or wait for the player to terminate using fluid_player_join().
 
@@ -621,7 +621,7 @@ int main(int argc, char** argv)
 
 
 
-\page Sequencer Sequencer
+\page Sequencer Using the MIDI sequencer
 
 FluidSynth's sequencer can be used to play MIDI events in a more flexible way than using the MIDI file player, which expects the events to be stored as Standard MIDI Files. Using the sequencer, you can provide the events one by one, with an optional timestamp for scheduling. 
 
@@ -747,7 +747,7 @@ int main(void) {
 The shell interface allows you to send simple textual commands to the synthesizer, to parse a command file, or to read commands from the stdin or other input streams. To find the list of currently supported commands, type @c help in the fluidsynth command line shell. For a full list of available <strong>command line settings</strong>, please refer to the \ref settings_shell documentation.
 
 
-\page Multi-channel Multi-Channel audio rendering
+\page Multi-channel Multi-channel audio rendering
 
 FluidSynth is capable of rendering all audio and all effects from all MIDI channels to separate stereo buffers. Refer to the documentation of fluid_synth_process() and review the different use-cases in the example file for information on how to do that: \ref fluidsynth_process.c
 
@@ -792,7 +792,7 @@ found in the API reference and in the GitHub Wiki.
 - Voice overflow settings
 - LADSPA effects unit
 - MIDI tunings
-*/
+
 
 /*!
 \example example.c