Upload folder using huggingface_hub

camel-camel-report-maven-plugin.md.md

@@ -503,7 +503,7 @@ comma.</p></td>
 <td style="text-align: left;"><p>anonymousRoutes</p></td>
 <td style="text-align: left;"><p>false</p></td>
 <td style="text-align: left;"><p>Whether to allow anonymous routes
-(routes without any route id assigned). By using route id’s then its
+(routes without any route id assigned). By using route id’s then it is
 safer to match the route cover data with the route source code.
 Anonymous routes are less safe to use for route coverage as its harder
 to know exactly which route that was tested corresponds to which of the

camel-choice-eip.md.md

@@ -171,9 +171,9 @@ based on [property
 placeholders](#manual:ROOT:using-propertyplaceholder.adoc).
 
 Here we select from the Switch the first predicate that matches. So if
-there is a property placeholder with the key `foo` then its select, and
-so on. Notice how we can use `{{?foo}}` to mark the property placeholder
-as optional.
+there is a property placeholder with the key `foo` then it is selected,
+and so on. Notice how we can use `{{?foo}}` to mark the property
+placeholder as optional.
 
 Java  
 from("direct:a")

camel-dead-letter-channel.md.md

@@ -84,11 +84,11 @@ much more similar than currently.
 ## Redelivery
 
 It is common for a temporary outage or database deadlock to cause a
-message to fail to process; but the chances are if its tried a few more
-times with some time delay then it will complete fine. So we typically
-wish to use some kind of redelivery policy to decide how many times to
-try to redeliver a message and how long to wait before redelivery
-attempts.
+message to fail to process; but the chances are if it is tried a few
+more times with some time delay then it will complete fine. So we
+typically wish to use some kind of redelivery policy to decide how many
+times to try to redeliver a message and how long to wait before
+redelivery attempts.
 
 The
 [RedeliveryPolicy](https://www.javadoc.io/doc/org.apache.camel/camel-base/current/org/apache/camel/processor/errorhandler/RedeliveryPolicy.html)

camel-java-xml-io-dsl.md.md

@@ -11,7 +11,7 @@ the `xml-io-dsl` is a source code generated parser that is Camel
 specific and can only parse Camel `.xml` route files (not classic Spring
 `<beans>` XML files).
 
-If you are using Camel XML DSL then its recommended using `xml-io-dsl`
+If you are using Camel XML DSL then it is recommended using `xml-io-dsl`
 instead of `xml-jaxb-dsl`. You can use this in all of Camel’s runtime
 such as Spring Boot, Quarkus, Camel Main, and Camel K etc.
 

camel-java-xml-jaxb-dsl.md.md

@@ -10,7 +10,7 @@ the `xml-io-dsl` is a source code generated parser that is Camel
 specific and can only parse Camel `.xml` route files (not classic Spring
 `<beans>` XML files).
 
-If you are using Camel XML DSL then its recommended using `xml-io-dsl`
+If you are using Camel XML DSL then it is recommended using `xml-io-dsl`
 instead of `xml-jaxb-dsl`. You can use this in all of Camel’s runtime
 such as Spring Boot, Quarkus, Camel Main, and Camel K etc.
 

camel-jms.md

@@ -1198,13 +1198,13 @@ processing in Camel, and we wait for a return reply:
 # Sending an InOnly message and keeping the JMSReplyTo header
 
 When sending to a [JMS](#jms-component.adoc) destination using
-**camel-jms**, the producer will use the MEP to detect if its *InOnly*
-or *InOut* messaging. However, there can be times when you want to send
-an *InOnly* message but keeping the `JMSReplyTo` header. To do so, you
+**camel-jms**, the producer will use the MEP to detect if it is `InOnly`
+or `InOut` messaging. However, there can be times when you want to send
+an `InOnly` message but keeping the `JMSReplyTo` header. To do so, you
 have to instruct Camel to keep it, otherwise the `JMSReplyTo` header
 will be dropped.
 
-For example, to send an *InOnly* message to the foo queue, but with a
+For example, to send an `InOnly` message to the foo queue, but with a
 `JMSReplyTo` with bar queue you can do as follows:
 
     template.send("activemq:queue:foo?preserveMessageQos=true", new Processor() {

camel-main.md.md

@@ -1353,11 +1353,11 @@ attempts.</p></td>
 <td
 style="text-align: left;"><p><strong>camel.routecontroller.enabled</strong></p></td>
 <td style="text-align: left;"><p>To enable using supervising route
-controller which allows Camel to startup and then the controller takes
+controller which allows Camel to start up and then, the controller takes
 care of starting the routes in a safe manner. This can be used when you
-want to startup Camel despite a route may otherwise fail fast during
-startup and cause Camel to fail to startup as well. By delegating the
-route startup to the supervising route controller then its manages the
+want to start up Camel despite a route may otherwise fail fast during
+startup and cause Camel to fail to start up as well. By delegating the
+route startup to the supervising route controller, then it manages the
 startup using a background thread. The controller allows to be
 configured with various settings to attempt to restart failing
 routes.</p></td>

camel-mongodb.md

@@ -101,7 +101,7 @@ can be anything that has an equivalent to a `Bson` type. See
         .to("mongodb:myDb?database=flights&collection=tickets&operation=findById")
         .to("mock:resultFindById");
 
-Please, note that the default \_id is treated by Mongo as and `ObjectId`
+Please note that the default \_id is treated by Mongo as and `ObjectId`
 type, so you may need to convert it properly.
 
     from("direct:findById")

camel-sql.md

@@ -49,7 +49,7 @@ precedence:
 
 1.  from a [Simple](#languages:simple-language.adoc) expressions
 
-2.  from message body if its a `java.util.Map`
+2.  from message body if it is a `java.util.Map`
 
 3.  from message headers
 

camel-xpath-language.md.md

@@ -313,7 +313,7 @@ The namespace builder supports adding multiple namespaces as shown:
                          .add("w", "http://acme.com/wine")
                          .add("b", "http://acme.com/beer");
 
-When using namespaces in XML DSL then its different, as you set up the
+When using namespaces in XML DSL then it is different, as you set up the
 namespaces in the XML root tag (or one of the `camelContext`, `routes`,
 `route` tags).
 

camel-xquery-language.md.md

@@ -70,7 +70,7 @@ access the value of <code>exchange.out.headers</code> with key
 and <code>exchange.in.headers</code> and any additional parameters set
 using <code>setParameters(Map)</code>. These parameters are added with
 their own key name, for instance, if there is an IN header with the key
-name <strong>foo</strong> then its added as
+name <strong>foo</strong> then it is added as
 <strong>foo</strong>.</p></td>
 </tr>
 </tbody>
@@ -127,7 +127,7 @@ The namespace builder supports adding multiple namespaces as shown:
                          .add("w", "http://acme.com/wine")
                          .add("b", "http://acme.com/beer");
 
-When using namespaces in XML DSL then its different, as you set up the
+When using namespaces in XML DSL then it is different, as you set up the
 namespaces in the XML root tag (or one of the `camelContext`, `routes`,
 `route` tags).
 

camel-xquery.md

@@ -77,7 +77,7 @@ which name is out.headers.foo variable</p></td>
 exchange.in.headers and any additional parameters set using
 <code>setParameters(Map)</code>. These parameters are added with their
 own key name, for instance, if there is an IN header with the key name
-<strong>foo</strong> then its added as <strong>foo</strong>.</p></td>
+<strong>foo</strong> then it is added as <strong>foo</strong>.</p></td>
 </tr>
 </tbody>
 </table>

camel-xslt-saxon.md

@@ -203,7 +203,7 @@ such as
 `"xslt-saxon:dummy.xsl?contentCache=false&allowTemplateFromHeader=true"`
 as this will tell Camel to not load `dummy.xsl` on startup but to load
 the stylesheet on demand. And because you provide the stylesheet via
-headers, then its fully dynamic.
+headers, then it is fully dynamic.
 
 # Accessing warnings, errors and fatalErrors from XSLT ErrorListener
 

camel-xslt.md

@@ -172,7 +172,7 @@ such as
 `"xslt:dummy.xsl?contentCache=false&allowTemplateFromHeader=true"` as
 this will tell Camel to not load `dummy.xsl` on startup but to load the
 stylesheet on demand. And because you provide the stylesheet via
-headers, then its fully dynamic.
+headers, then it is fully dynamic.
 
 # Accessing warnings, errors and fatalErrors from XSLT ErrorListener