chore(doc): fix links to unlock website
@@ -110,7 +110,7 @@ spec:
json: {}
- to: "kamelet:sink" # <5>
----
-<1> `keywords` is a path parameter in https://camel.apache.org/components/latest/twitter-search-component.html[Camel Twitter-search]
+<1> `keywords` is a path parameter in xref:latest@components::twitter-search-component.adoc[Camel Twitter-search]
<2> Some endpoint parameters are just mapped 1-1
<3> The Camel component `consumerKey` is named `apiKey` to reflect the actual name in the Twitter developer portal
<4> The Camel Twitter component generates Java objects, so we marshal them to JSON
@@ -454,7 +454,7 @@ Since the integration above produces useful data, its route could be technically
as much as possible. We can think to store the time when the last update has been generated by the server and use it in subsequent queries to only obtain new events.
This will not guarantee an "exactly once" semantics, because e.g. if the integration is restarted it will lose the in-memory state and start from the beginning,
but it prevents sending an high amount of redundant data if the integration is kept alive.
-To store the time when last result has been generated by the API, we can use one of the in-memory caches that Camel provides, such as https://camel.apache.org/components/latest/caffeine-cache-component.html[camel-caffeine-cache].
+To store the time when last result has been generated by the API, we can use one of the in-memory caches that Camel provides, such as xref:latest@components::caffeine-cache-component.adoc[camel-caffeine-cache].
WARNING: We're going to use an in-memory cache because we need to store a single value. When using stateful data repositories, such as caches, it's always a good practice to limit their size to a low value and avoid them to increase their size over time
@@ -929,7 +929,7 @@ In order to implement sending different kinds of data, the Kamelet should adapt
We'll start by writing an end-to-end integration, then we'll convert it into a Kamelet. This time, we'll write routes directly in YAML DSL.
-TIP: For this particular use case, I've created a simple integration before to get the Chat ID corresponding to my phone from the bot: more info https://camel.apache.org/components/latest/telegram-component.html#_getting_the_chat_id[here].
+TIP: For this particular use case, I've created a simple integration before to get the Chat ID corresponding to my phone from the bot: more info xref:latest@components::telegram-component.adoc[here].
Let's start with a simple integration:
