This is an automated email from the ASF dual-hosted git repository.
zregvart pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit f4cf51358ef375c62ba680f2781660ae22e47685
Author: nayananga@acerubuntu18.04 <nayanangamuhandi...@gmail.com>
AuthorDate: Thu Jul 18 12:03:16 2019 +0530
more fixes for anchor not found errors
---
components/camel-cxf/src/main/docs/cxf-component.adoc | 2 +-
components/camel-micrometer/src/main/docs/micrometer-component.adoc | 2 +-
docs/components/modules/ROOT/pages/cxf-component.adoc | 2 +-
docs/components/modules/ROOT/pages/micrometer-component.adoc | 2 +-
...-and-how-do-i-let-the-file-consumer-use-the-camel-error-handler.adoc | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/components/camel-cxf/src/main/docs/cxf-component.adoc
b/components/camel-cxf/src/main/docs/cxf-component.adoc
index c4c5804..38f3e9f 100644
--- a/components/camel-cxf/src/main/docs/cxf-component.adoc
+++ b/components/camel-cxf/src/main/docs/cxf-component.adoc
@@ -24,7 +24,7 @@ hosted in CXF.
**** <<How to enable CXF's LoggingOutInterceptor in MESSAGE mode>>
*** <<Description of relayHeaders option>>
**** <<Available only in POJO mode>>
-**** <<Changes since Release 2.0>>
+**** Changes since Release 2.0
** <<Configure the CXF endpoints with Spring>>
** <<Configuring the CXF Endpoints with Apache Aries Blueprint>>
** <<How to make the camel-cxf component use log4j instead of
java.util.logging>>
diff --git
a/components/camel-micrometer/src/main/docs/micrometer-component.adoc
b/components/camel-micrometer/src/main/docs/micrometer-component.adoc
index 164f4df..490c672 100644
--- a/components/camel-micrometer/src/main/docs/micrometer-component.adoc
+++ b/components/camel-micrometer/src/main/docs/micrometer-component.adoc
@@ -196,7 +196,7 @@ class MyBean extends RouteBuilder {
Each meter has type and name. Supported types are
xref:#MicrometerComponent-counter[counter],
xref:#MicrometerComponent-summary[distribution summary] and
-xref:#MetricsComponent-timer[timer]. If no type is provided then a counter is
used by default.
+timer. If no type is provided then a counter is used by default.
The meter name is a string that is evaluated as `Simple` expression. In
addition to using the `CamelMetricsName`
header (see below), this allows to select the meter depending on exchange data.
diff --git a/docs/components/modules/ROOT/pages/cxf-component.adoc
b/docs/components/modules/ROOT/pages/cxf-component.adoc
index c4c5804..38f3e9f 100644
--- a/docs/components/modules/ROOT/pages/cxf-component.adoc
+++ b/docs/components/modules/ROOT/pages/cxf-component.adoc
@@ -24,7 +24,7 @@ hosted in CXF.
**** <<How to enable CXF's LoggingOutInterceptor in MESSAGE mode>>
*** <<Description of relayHeaders option>>
**** <<Available only in POJO mode>>
-**** <<Changes since Release 2.0>>
+**** Changes since Release 2.0
** <<Configure the CXF endpoints with Spring>>
** <<Configuring the CXF Endpoints with Apache Aries Blueprint>>
** <<How to make the camel-cxf component use log4j instead of
java.util.logging>>
diff --git a/docs/components/modules/ROOT/pages/micrometer-component.adoc
b/docs/components/modules/ROOT/pages/micrometer-component.adoc
index 164f4df..490c672 100644
--- a/docs/components/modules/ROOT/pages/micrometer-component.adoc
+++ b/docs/components/modules/ROOT/pages/micrometer-component.adoc
@@ -196,7 +196,7 @@ class MyBean extends RouteBuilder {
Each meter has type and name. Supported types are
xref:#MicrometerComponent-counter[counter],
xref:#MicrometerComponent-summary[distribution summary] and
-xref:#MetricsComponent-timer[timer]. If no type is provided then a counter is
used by default.
+timer. If no type is provided then a counter is used by default.
The meter name is a string that is evaluated as `Simple` expression. In
addition to using the `CamelMetricsName`
header (see below), this allows to select the meter depending on exchange data.
diff --git
a/docs/user-manual/modules/ROOT/pages/faq/why-does-my-file-consumer-not-pick-up-the-file-and-how-do-i-let-the-file-consumer-use-the-camel-error-handler.adoc
b/docs/user-manual/modules/ROOT/pages/faq/why-does-my-file-consumer-not-pick-up-the-file-and-how-do-i-let-the-file-consumer-use-the-camel-error-handler.adoc
index 83393b5..fcb3b19 100644
---
a/docs/user-manual/modules/ROOT/pages/faq/why-does-my-file-consumer-not-pick-up-the-file-and-how-do-i-let-the-file-consumer-use-the-camel-error-handler.adoc
+++
b/docs/user-manual/modules/ROOT/pages/faq/why-does-my-file-consumer-not-pick-up-the-file-and-how-do-i-let-the-file-consumer-use-the-camel-error-handler.adoc
@@ -4,7 +4,7 @@
There could be several reasons why the xref:file-component.adoc[File] consumer
is
not picking up files. For example it may not run at all, or it cannot
acquire a read lock on the file.
-xref:faq.adoc#logging-questions[Check the logs] for any exceptions or other
+xref:faq.adoc#FAQ-LoggingQuestions[Check the logs] for any exceptions or other
informative messages. You can
xref:how-do-i-enable-debug-logging.adoc[turn on DEBUG logging] at
`org.apache.camel.component.file` to see more detail.
