corrections as per review comments

topics/oidc/java/jboss-adapter.adoc

@@ -174,7 +174,7 @@ public class CustomerService {
 This section describes how to secure a WAR directly by adding config and editing files within your WAR package. 
 
 The first thing you must do is create a `keycloak.json` adapter config file within the `WEB-INF` directory of your WAR.
-The format of this config file is describe in the <<_saml-general-config,general adapter configuration>> section.
+The format of this config file is describe in the <<_java_adapter_config,general adapter configuration>> section.
 
 Next you must set the `auth-method` to `KEYCLOAK` in `web.xml`.
 You also have to use standard servlet security to specify role-base constraints on your URLs.
@@ -259,7 +259,7 @@ This metadata is instead defined within server configuration (i.e. `standalone.x
 
 The `secure-deployment` `name` attribute identifies the WAR you want to secure.
 Its value is the `module-name` defined in `web.xml` with `.war` appended.
-The rest of the configuration corresponds pretty much one to one with the `keycloak.json` configuration options defined in <<_saml-general-config,general adapter configuration>>.
+The rest of the configuration corresponds pretty much one to one with the `keycloak.json` configuration options defined in <<_java_adapter_config,general adapter configuration>>.
 The exception is the `credential` element. 
 
 To make it easier for you, you can go to the {{book.project.title}} Administration Console and go to the Application/Installation tab of the application this WAR is aligned with.

topics/oidc/java/jetty9-adapter.adoc

@@ -1,4 +1,3 @@
-
 [[_jetty9_adapter]]
 === Jetty 9.x Adapters
 
@@ -6,7 +5,7 @@ Keycloak has a separate adapter for Jetty 9.1.x and Jetty 9.2.x that you will ha
 You then have to provide some extra configuration in each WAR you deploy to Jetty.
 Let's go over these steps. 
 
-[[_jetty9_adapter_installation]]
+[[_jetty-9_adapter_installation]]
 ==== Adapter Installation
 
 Adapters are no longer included with the appliance or war distribution.Each adapter is a separate download on the Keycloak download site.
@@ -58,7 +57,7 @@ This is a Jetty specific config file and you must define a Keycloak specific aut
 ----
 
 Next you must create a `keycloak.json` adapter config file within the `WEB-INF` directory of your WAR.
-The format of this config file is describe in the <<_saml-general-config,general adapter configuration>>            section. 
+The format of this config file is describe in the <<_java_adapter_config,general adapter configuration>>            section. 
 
 WARNING: The Jetty 9.1.x adapter will not be able to find the `keycloak.json` file.
 You will have to define all adapter settings within the `jetty-web.xml` file as described below. 

topics/oidc/java/servlet-filter-adapter.adoc

@@ -31,7 +31,7 @@ There's no way standard way to invalidate an HTTP session based on a session id.
 ----
 
 In the snippet above there are two url-patterns.
- */protected/** are the files we want protected, while the */keycloak/** url-pattern handles callbacks from the {{book.project.title}} server.
+ _/protected/*_ are the files we want protected, while the _/keycloak/*_ url-pattern handles callbacks from the {{book.project.title}} server.
 
 Note that you should configure your client in the {{book.project.title}} Admin Console with an Admin URL that points to a secured section covered by the filter's url-pattern.
 

topics/oidc/java/tomcat-adapter.adoc

@@ -45,7 +45,7 @@ This is a Tomcat specific config file and you must define a Keycloak specific Va
 ----
 
 Next you must create a `keycloak.json` adapter config file within the `WEB-INF` directory of your WAR.
-The format of this config file is describe in the <<_saml-general-config,general adapter configuration>>            section. 
+The format of this config file is describe in the <<_java_adapter_config,general adapter configuration>>            section. 
 
 Finally you must specify both a `login-config` and use standard servlet security to specify role-base constraints on your URLs.
 Here's an example: 

topics/oidc/oidc-overview.adoc

@@ -1,4 +1,6 @@
 == OpenID Connect
 
 This section describes how you can secure applications and services with OpenID Connect using either {{book.project.name}} adapters or generic OpenID Connect
-Resource Provider libraries.
+Resource Provider libraries.
+
+// TODO: Update the cross-reference <<_direct_access_grants,Direct Access Grants>>  in the topic /oidc/java/fuse-adapter.adoc 

topics/saml/java/jetty-adapter/jetty9_installation.adoc

@@ -1,4 +1,4 @@
-[[_jetty_adapter_installation]]
+[[_jetty9_adapter_installation]]
 
 ===== Jetty 9 Adapter Installation