Deployed cfd1d8a with MkDocs version: 1.4.2

Reporting/Custom-Report-Tutorial/index.html

@@ -4843,7 +4843,7 @@ <h3 id="types-of-report-section">Types of Report Section<a class="headerlink" hr
 <p>There are two types of report section that you can use in your report:</p>
 <ul>
 <li>A <strong>standard section</strong> basically uses an existing pre-defined query that returns back some structured XML data from Spira. For example the 'Project Overview' section will include the project name, description and other meta-data and the 'Requirements Summary' section will include an XML representation of all the requirements in the project together with any child data nested (e.g. all of tasks that belong to a requirement or the list of comments, etc.). A key aspect of a standard section is that the data itself is not customizable, but you can change the XML Template (XSLT) that is used to extract the data and convert it into a viewable form. So you have the ability to use XSLT to transform the data. You also allow the user who runs the report to use the standard set of filters on the data (e.g. return only requirements in release 1.0 or test cases that are priority 1,2,3)</li>
-<li>On the other hand, a <strong>custom section</strong>, lets you use a custom database query using the <strong>Microsoft Entity SQL (ESQL)</strong> language to query the different database view in the system join records, aggregate data to generate a completely custom table of data that you can then transform using an <strong>XML template</strong> (XSLT) to display it in a specific form (e.g. a table of  data, a simple list, etc.). So you have the ability to two two tools: ESQL and XSLT to generate the report. The advantage over the standard section is that you are not limited to the queries that we have already defined in the system, but a custom section does not provide filter options for the end user.</li>
+<li>On the other hand, a <strong>custom section</strong>, lets you use a custom database query using the <strong>Microsoft Entity SQL (ESQL)</strong> language to query the different database view in the system join records, aggregate data to generate a completely custom table of data that you can then transform using an <strong>XML template</strong> (XSLT) to display it in a specific form (e.g. a table of  data, a simple list, etc.). So you have the ability to use two tools: ESQL and XSLT to generate the report. The advantage over the standard section is that you are not limited to the queries that we have already defined in the system, but a custom section does not provide filter options for the end user.</li>
 </ul>
 <p>A report you create can have a mixture of the two sections, for example you could start the report with the standard project name and description and follow that with a custom section that displays a table of custom data (e.g. a risk cube or other table of data).</p>
 <h2 id="how-to-create-and-edit-a-custom-report">How to Create and Edit a Custom Report<a class="headerlink" href="#how-to-create-and-edit-a-custom-report" title="Permanent link">&para;</a></h2>
@@ -5175,8 +5175,6 @@ <h3 id="viewing-the-data-available-for-reporting">Viewing the Data Available for
 </code></pre></div>
 <p>This fragment of the report lets you see all of the data that is available for displaying in your report. You can navigate this hierarchy of information using the special XSLT selection language called XPATH. This lets you query the data returned from Spira to retrieve specific data elements that can be displayed in the report. Before we start modifying the report XSLT to use this data, we first need to get a basic understanding of XPATH itself.</p>
 <h3 id="understanding-xpath">Understanding XPATH<a class="headerlink" href="#understanding-xpath" title="Permanent link">&para;</a></h3>
-<p>(this section includes material from the website:
-<a href="http://www.whoishostingthis.com/resources/xslt/">http://www.whoishostingthis.com/resources/xslt/</a>)</p>
 <p>XPath is used to navigate through elements and attributes in an XML document. XPath uses path expressions to select nodes or node-sets in an XML document. These path expressions look very much like the expressions you see when you work with a traditional computer file system.</p>
 <p>In XPath, there are seven kinds of nodes:</p>
 <ol>