[camel-kafka-connector] branch master updated: Document update

[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-kafka-connector.git


The following commit(s) were added to refs/heads/master by this push:
     new c18a2d4  Document update
     new 3849a1c  Merge pull request #464 from NiteshKoushik/patch-3
c18a2d4 is described below

commit c18a2d4f7a3304965da0af619b2452d38208eec0
Author: Nitesh Koushik S <39...@users.noreply.github.com>
AuthorDate: Wed Sep 16 10:29:05 2020 +0530

    Document update
    
    Changes made from "service allow different" to “service allows different”
---
 docs/modules/ROOT/pages/testing.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/modules/ROOT/pages/testing.adoc b/docs/modules/ROOT/pages/testing.adoc
index ce4de58..cc82ecd 100644
--- a/docs/modules/ROOT/pages/testing.adoc
+++ b/docs/modules/ROOT/pages/testing.adoc
@@ -143,7 +143,7 @@ For example, when handling credentials or different communication protocols that
 might make sense to abstract that logic from the test code.
 
 A specialized service factory class is responsible for creating the service according to runtime parameters and/or
-other test scenarios constraints. When a service allow different service types or locations to be selected, this
+other test scenarios constraints. When a service allows different service types or locations to be selected, this
 should be done via command line properties (`-D<property.name>=<value>`). For example, when allowing a service to choose
 between running as a local container or as remote instance, a property in the format `<name>.instance.type` should be
 handled. Additional runtime parameters used in different scenarios, should be handled as `<name>.<parameter>`.