deegree#858 - minor improvements

deegree-services/deegree-webservices-handbook/src/main/asciidoc/basics.adoc

@@ -118,8 +118,7 @@ read/write access to this directory.
 
 ==== Global configuration files and the active workspace
 
-If you downloaded all four example workspaces (as described in
-_anchor-lightly_), set a console password and the proxy parameters,
+If you downloaded all four example workspaces (as described in <<anchor-lightly>>), set a console password and the proxy parameters,
 your _.deegree_ directory will look like this:
 
 .Example _.deegree_ directory

deegree-services/deegree-webservices-handbook/src/main/asciidoc/coveragestores.adoc

@@ -180,12 +180,12 @@ store.
 If your GeoRaster coverage only consist in a greyscale coverage or you
 only want to server a single band you could specifiy the following:
 
-[source,xml
+[source,xml]
+----
 <Bands>
 <Single>1</Single>
 </Bands>]
 ----
-----
 
 [width="100%",cols="20%,11%,7%,62%",options="header",]
 |===

deegree-services/deegree-webservices-handbook/src/main/asciidoc/featurestores.adoc

@@ -1756,7 +1756,7 @@ The SQL feature store always tries to map filter conditions (e.g. from
 WFS _GetFeature_ requests or when accessed by the WMS) to SQL-WHERE
 conditions. However, this is not possible in all cases. Sometimes a
 filter uses an expression that does not have an equivalent SQL-WHERE
-clause. For example when using _anchor-blob-mode_ and the filter is
+clause. For example when using <<anchor-blob-mode>> and the filter is
 not based on a feature id or a spatial constraint.
 
 In such cases, the SQL feature store falls back to in-memory filtering.

deegree-services/deegree-webservices-handbook/src/main/asciidoc/filterencoding.adoc

@@ -5,8 +5,7 @@ deegree makes extensive use of the OGC Filter Encoding standard. Within
 deegree there are implementations of the versions 1.1.0 and 2.0.0 of
 this standards and several extensions and additional functions. This
 chapter is meant to explain the filter capabilities of deegree which can
-be used within <<anchor-configuration-renderstyles>> and
-:ref:`anchor-configuration-wfs´ requests.
+be used within <<anchor-configuration-renderstyles>> and <<anchor-configuration-wfs>> requests.
 
 === Filter Operators
 

deegree-services/deegree-webservices-handbook/src/main/asciidoc/installation.adoc

@@ -123,7 +123,7 @@ http://tomcat.apache.org/tomcat-8.5-doc/ssl-howto.html[SSL HowTo].
 
 It is as a huge security problem to operate the deegree web app without
 setting a password for the deegree console. How to set the password for
-the deegree console is described in _anchor-configuration-basics>>. The
+the deegree console is described in <<anchor-configuration-basics>>. The
 same applies to the deegree REST API. Since both transfer the
 credentials as clear text (with a little bit of obscurity) it is highly
 recommended to enable encryption on the protocol level as described

deegree-services/deegree-webservices-handbook/src/main/asciidoc/javamodules.adoc

@@ -98,6 +98,7 @@ to add additional Java libraries manually, as the required JDBC
 libraries are not included in the deegree webservices download (for
 license reasons).
 
+[[anchor-oraclejars]]
 ==== Adding Oracle support
 
 The following deegree resources support Oracle Spatial databases:
@@ -109,7 +110,7 @@ The following deegree resources support Oracle Spatial databases:
 In order to enable Oracle connectivity for these resources, you need to
 add two JAR files (see <<anchor-adding-jars>>):
 
-* A compatible Oracle JDBC8-type driver (e.g.
+* A compatible Oracle JDBC driver (e.g.
 _ojdbc8.jar_)footnote:[http://www.oracle.com/technetwork/database/features/jdbc/index-091264.html
 (registration required)]
 * Module
@@ -123,8 +124,7 @@ in Oracle databases.
 In order to enable Oracle connectivity for these resources, you need to
 add the following JAR files (see <<anchor-adding-jars>>):
 
-* A compatible Oracle JDBC-type
-driverfootnote:[http://www.oracle.com/technetwork/database/features/jdbc/index-091264.html
+* A compatible Oracle JDBC-driverfootnote:[http://www.oracle.com/technetwork/database/features/jdbc/index-091264.html
 (registration required)]
 ** ojdbc8.jar
 * The Oracle Spatial and GeoRaster libraries and their dependencies

deegree-services/deegree-webservices-handbook/src/main/asciidoc/webservices.adoc

@@ -1831,14 +1831,14 @@ layer metadata
 Below the _ServiceConfiguration_ section you can specify custom
 featureinfo format handlers:
 
-[source,xml
+[source,xml]
+----
 ...
 </ServiceConfiguration>
 <FeatureInfoFormats>
 ...
 </FeatureInfoFormats>]
 ----
-----
 
 Have a look at section <<anchor-featureinfo-configuration>> (in the WMS
 chapter) to see how custom featureinfo formats are configured. Take note