[camel] 02/07: Camel-FTP: Fixed tip section

[ac...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git

commit d991e884735fd91c5fb0cfe3b70f9e65f67a3695
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Mon Jan 13 09:05:18 2020 +0100

    Camel-FTP: Fixed tip section
---
 components/camel-ftp/src/main/docs/ftp-component.adoc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/components/camel-ftp/src/main/docs/ftp-component.adoc b/components/camel-ftp/src/main/docs/ftp-component.adoc
index 5d0733a..96879e8 100644
--- a/components/camel-ftp/src/main/docs/ftp-component.adoc
+++ b/components/camel-ftp/src/main/docs/ftp-component.adoc
@@ -448,13 +448,13 @@ as files then you need to route to a file endpoint such as:
 from("ftp://someone@someserver.com?password=secret&localWorkDirectory=/tmp").to("file://inbox");
 ----
 
-[TIP, caption='Optimization by renaming work file']
-===
+[TIP]
+====
 The route above is ultra efficient as it avoids reading the entire file content into memory.
 It will download the remote file directly to a local file stream.
 The `java.io.File` handle is then used as the Exchange body. The file producer leverages this fact and can work directly on the work file `java.io.File` handle and perform a `java.io.File.rename` to the target filename.
 As Camel knows it's a local work file, it can optimize and use a rename instead of a file copy, as the work file is meant to be deleted anyway.
-===
+====
 
 == Stepwise changing directories