Update text Getting Started because FixedResultPipe replaced

docs/source/deploying/security.rst

@@ -11,7 +11,7 @@ The previous section was about fine-tuning the Frank!Framework. You learned abou
 There are two ways of configuring security for your application: Containerized Authentication (new) and JEE Provided Authentication (old). Containerized Authentication uses properties in the Frank!Framework to set up authentication and is the recommended way of setting up authentication. JEE Provided Authentication is based on Java EE ApplicationServers and cannot be used in containerized environments.
 
 Containerized Authentication
--------------------------------
+----------------------------
 
 To add authentication to your Frank!Console Open your ``DeploymentSpecifics.properties`` and add the following lines of code:
 
@@ -82,7 +82,7 @@ Below is a table containing all authenticator types and their properties.
 
 
 JEE Provided Authentication (Deprecated since v8.0.0)
--------------------------------
+-----------------------------------------------------
 
 .. highlight:: none
 

docs/source/gettingStarted/horizonsInsertDb.rst

@@ -15,7 +15,7 @@ As an example, we extend the New Horizons case by writing the "booking" table in
 
    .. include:: ../snippets/NewHorizons/v460/refSenderPipe.txt
 
-#. Insert the new pipe after the ``</FixedResultPipe>``:
+#. Insert the new pipe after the ``</EchoPipe>``:
 
    .. include:: ../snippets/NewHorizons/v460/addSenderPipe.txt
 

docs/source/gettingStarted/testPipelines.rst

@@ -23,7 +23,7 @@ See the figure below:
 
 .. image:: ladybugSummary.jpg
 
-You can examine your pipeline runs by choosing "Testing | Ladybug" from the main menu. You have feedback that you chose that option (number 1). Next, press "Refresh" (number 2) to update the overview of your runs. The figure shows only one report (number 3). Usually, you can use the "EndTime" and the adapter "Name" columns to find the report you want. Click that row to view it in the bottom-left tree-view. You can expand and collapse the pipeline and the pipes it contains. For each node, you can see the input or output message by selecting it. By selecting number 4, you see the input message of the pipeline. The output message of the pipeline is at node 7. The input and the output of the only pipe, the ``<FixedResultPipe>``, are at nodes 5 and 6. Information about the chosen node can be seen to the right: number 8 shows the message.
+You can examine your pipeline runs by choosing "Testing | Ladybug" from the main menu. You have feedback that you chose that option (number 1). Next, press "Refresh" (number 2) to update the overview of your runs. The figure shows only one report (number 3). Usually, you can use the "EndTime" and the adapter "Name" columns to find the report you want. Click that row to view it in the bottom-left tree-view. You can expand and collapse the pipeline and the pipes it contains. For each node, you can see the input or output message by selecting it. By selecting number 4, you see the input message of the pipeline. The output message of the pipeline is at node 7. The input and the output of the only pipe, the ``<EchoPipe>``, are at nodes 5 and 6. Information about the chosen node can be seen to the right: number 8 shows the message.
 
 Ladybug has many functions. It is explained in detail in chapter :ref:`ladybug`.