[camel-website] branch correct-typos updated (7d0f815 -> 3c228f1)

[bv...@apache.org]

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

bvahdat pushed a change to branch correct-typos
in repository https://gitbox.apache.org/repos/asf/camel-website.git.


 discard 7d0f815  better point out the BOM availability starting from 3.8.0
 discard 289b4cc  2 tiny adjustments
     new 3c228f1  2 tiny adjustments

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (7d0f815)
            \
             N -- N -- N   refs/heads/correct-typos (3c228f1)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:

[camel-website] 01/01: 2 tiny adjustments

[bv...@apache.org]

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

bvahdat pushed a commit to branch correct-typos
in repository https://gitbox.apache.org/repos/asf/camel-website.git

commit 3c228f11de1cc4309c55c6fe969c895062bf7352
Author: Babak Vahdat <bv...@apache.org>
AuthorDate: Sat Feb 27 19:28:50 2021 +0100

    2 tiny adjustments
---
 content/blog/2021/02/Camel38-Whatsnew/index.md | 2 +-
 layouts/partials/releases/camel.html           | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/content/blog/2021/02/Camel38-Whatsnew/index.md b/content/blog/2021/02/Camel38-Whatsnew/index.md
index ea9c935..1d8a8bc 100644
--- a/content/blog/2021/02/Camel38-Whatsnew/index.md
+++ b/content/blog/2021/02/Camel38-Whatsnew/index.md
@@ -88,7 +88,7 @@ Speaking of YAML that brings us to the next feature - Kamelets.
 The `camel-kamelet` component has been stabilized as part of Camel K and is now ready
 and have been ported over to the main Camel project.
 
-There is a [little example here](https://github.com/apache/camel-examples/tree/master/examples/camel-example-kamelet)
+There is a [little example here](https://github.com/apache/camel-examples/tree/master/examples/kamelet)
 of using Kamelet in vanilla Camel.
 
 We have previously introduced Kamelet, which was created in Camel K.
diff --git a/layouts/partials/releases/camel.html b/layouts/partials/releases/camel.html
index ba0ca21..3d4a928 100644
--- a/layouts/partials/releases/camel.html
+++ b/layouts/partials/releases/camel.html
@@ -30,6 +30,7 @@
 <p>To use this release in a Spring Boot application, use the <code>camel-spring-boot-dependencies</code> Bill of Materials (BOM):
 <aside>
   <p><mark>Note:</mark> for Camel 3.0.0 and newer releases the <code>groupId</code> for Camel Spring Boot support changed from <code>org.apache.camel</code> to <code>org.apache.camel.springbooot</code>, so be sure to check that the appropriate <code>groupId</code> is used for the Camel version.</p>
+  <p><mark>Note:</mark> for Camel 3.8.0 and newer releases there is another BOM available with the <code>artifactId</code> of <code>camel-spring-boot-bom</code> which you could instead make use of. For details see <a href="camel-spring-boot/latest/#_camel_spring_boot_bom_vs_camel_spring_boot_dependencies_bom">the corresponding documentation</a></p>
   <p>Replace the <code>COMPONENT</code> with the artifact outlined in the <a href="/components/latest/">component documentation</a></p>
 </aside>
 <pre><code>{{ htmlUnescape (printf `<dependencyManagement>