Fix underlines.

source/03-indexing_marc_records.rst

@@ -38,7 +38,7 @@ Once the indexing process is complete, you should be able to return to http://lo
 SolrMarc maps MARC records into Solr using configuration files, and the defaults that ship with VuFind® should meet most needs. However, most users will want to customize at least some fields, and in some situations, customizations will be necessary for successful record loading. Before getting into the details of SolrMarc customization, however, it is important to understand how VuFind® stores and loads its configuration files.
 
 3.3 Understanding VuFind®’s “Local Directory”
---------------------------------------------
+---------------------------------------------
 
 In section 2.2.1, it was mentioned that installing VuFind® with a Debian package sets up two environment variables on your system: $VUFIND_HOME and $VUFIND_LOCAL_DIR. $VUFIND_HOME contains the full path to the directory containing the VuFind® software (/usr/local/vufind by default); $VUFIND_LOCAL_DIR contains the full path to VuFind®’s “local directory” (by default, /usr/local/vufind/local).
 

source/05-understanding_solr.rst

@@ -202,7 +202,7 @@ The QueryFields section specifies which field or fields will be searched, and wh
 Fortunately, because DisMax provides a much simpler configuration and works for the majority of cases, it is rare that users need to work with or understand these older munge-based search types; however, a basic understanding of how to read them may be helpful, especially if you are troubleshooting a search that uses them. Call Number searching is probably the most common remaining use case for this type of search configuration.
 
 5.3 Troubleshooting Solr with VuFind®’s Debug Mode
--------------------------------------------------
+--------------------------------------------------
 
 As mentioned earlier, VuFind® does the hard work of interacting with Solr for you, and exposes most of the options you will need through configuration files. When you perform a search in VuFind®, it translates your query into a Solr query according to the rules defined in its configuration files, then uses that query to retrieve search results, and finally formats those results into the web page that you end up seeing.
 

source/10-content_harvesting.rst

@@ -23,7 +23,7 @@ VuFind® can act as an OAI-PMH service provider, because it includes tools for h
 
 
 10.2 VuFind®’s OAI-PMH Harvester
--------------------------------
+--------------------------------
 
 VuFind®’s OAI-PMH harvester is a command line tool which allows you to harvest metadata from an OAI- PMH data provider into a directory of files on your local disk. This directory can then be indexed into VuFind® using the processes described in chapter 11. Rules for harvesting can be specified directly on the command line through a variety of options and switches, or they can be stored in the $VUFIND_LOCAL_DIR/harvest/oai.ini file. The oai.ini method is generally more convenient, and that is the approach that will be described here.  
 
@@ -167,7 +167,7 @@ ___________
 The OJS (Open Journal System) publishing platform includes built-in OAI-PMH data provider support as well as a metadata plug-in system which makes it possible to add support for custom metadata formats. VuFind® includes sample import rules for both the Dublin Core and NLM (National Library of Medicine) formats.
 
 10.4 VuFind®’s OAI-PMH Server
-____________________________
+_____________________________
 
 In addition to consuming OAI-PMH records, VuFind® can also produce them. While VuFind®’s OAI-PMH data provider server is turned off by default, it can be activated by uncommenting and filling in the [OAI] section of config.ini. All of the available settings are described by comments in the .ini file; none are required (simply uncommenting the [OAI] section header is enough to turn on the server), but setting an identifier and repository_name are strongly recommended. Other settings exist to give you control over how your OAI-PMH server presents record sets and metadata formats.
 

source/11-xml_indexing.rst

@@ -24,7 +24,7 @@ Writing your own XSLT sheets and custom PHP functions is beyond the scope of thi
 If you want to gain a deeper understanding of the XSLT language, numerous helpful books and online articles exist. Just be sure to check which version of the standard is being discussed, since articles about XSLT 2.0 and newer may include some information that will not apply to VuFind®’s basic XSLT 1.0 interpreter. Doug Tidwell’s XSLT, published by O’Reilly, is a thorough guidebook and reference; the first edition of the book (published in 2001) covers XSLT 1.0, while the second edition (published in 2009) discusses both 1.0 and 2.0.
 
 11.2 VuFind®’s Command-Line XSLT Indexer
----------------------------------------
+----------------------------------------
 
 VuFind®’s XSLT indexing tool is found at $VUFIND_HOME/import/import-xsl.php. It can be run from the command line like this:
 

source/16-introduction_to_laminas.rst

@@ -52,7 +52,7 @@ Code modules are also a way of sharing functionality between Laminas-based appli
 If you are interested in seeing exactly how VuFind® loads its modules, take a look at the $VUFIND_HOME/config/application.config.php file, which contains most of the high-level Laminas application setup logic.
 
 16.3.2 VuFind®’s Built-In Modules
-________________________________
+_________________________________
 
 VuFind® contains several code modules, found under the $VUFIND_HOME/modules directory; as of release 7.0, they are: