Changed pass to the correct format

Signed-off-by: David Kral <[email protected]>

docs/src/main/asciidoc/mp/config/advanced-configuration.adoc

@@ -87,7 +87,7 @@ include::{sourcedir}/mp/config/AdvancedConfigurationSnippets.java[tag=snippet_2,
 Custom Config Sources are loaded using the Java Service Loader pattern, by implementing
 either `org.eclipse.microprofile.config.spi.ConfigSource`,
 or `org.eclipse.microprofile.config.spi.ConfigSourceProvider` SPI and registering
-it as a service (Using `pass:[META-INF/services/${class-name}]` file when using classpath, or
+it as a service (Using pass:normal[`META-INF/services/${class-name}`] file when using classpath, or
 using the `provides` statement in `module-info.java` when using module path).
 
 The interface `org.eclipse.microprofile.config.spi.ConfigSource` requires implementation of the following methods:
@@ -172,7 +172,7 @@ sources:
 
 == Extending Meta-Config to Create a Custom Config Source Type
 
-Helidon meta-config by default supports the following types: environment-variables, system-properties, properties, yaml, hocon and json. Users can also extend meta-config to create a custom config source type by loading it using the Java Service Loader pattern. This is achieved  by implementing `io.helidon.config.mp.spi.MpMetaConfigProvider` SPI and registering it as a service (Using `pass:[META-INF/services/${class-name}]` file when using classpath, or using the `provides` statement in `module-info.java` when using module path).
+Helidon meta-config by default supports the following types: environment-variables, system-properties, properties, yaml, hocon and json. Users can also extend meta-config to create a custom config source type by loading it using the Java Service Loader pattern. This is achieved  by implementing `io.helidon.config.mp.spi.MpMetaConfigProvider` SPI and registering it as a service (Using pass:normal[`META-INF/services/${class-name}`] file when using classpath, or using the `provides` statement in `module-info.java` when using module path).
 
 The interface `io.helidon.config.mp.spi.MpMetaConfigProvider` requires implementation of the following methods:
 

docs/src/main/asciidoc/se/config/advanced-configuration.adoc

@@ -486,7 +486,7 @@ for more detail.
 
 === Tokens
 A token reference is a key token starting with `$`, optionally enclosed between
- `{` and `}`, i.e. `$ref`, `pass:[${ref}]`. Even a key composed of more than one token
+ `{` and `}`, i.e. `$ref`, pass:normal[`${ref}`]. Even a key composed of more than one token
  can be referenced in another key, i.e. `${env.ref}`.
 
 As an example use case, you can use token references to declare the default values (see

docs/src/main/asciidoc/se/guides/webclient.adoc

@@ -196,7 +196,7 @@ Hello David!
 ----
 
 It is also possible to change the greeting word by using a PUT request to `/greet/greeting` path. The request also
-needs to include a body with JSON type and using a structure like `pass:[{"greeting" : "value"}]`.
+needs to include a body with JSON type and using a structure like pass:normal[`{"greeting" : "value"}`].
 
 [source,java]
 .Modify the application greeting: