From c978eea5a2f4a6cbc81c4c61a67db46bfbf255c7 Mon Sep 17 00:00:00 2001 From: Document Doctor Date: Sat, 12 Jan 2019 17:12:53 -0500 Subject: [PATCH] Fixed typos in README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 807744f..4a872fc 100644 --- a/README.md +++ b/README.md @@ -12,7 +12,7 @@ Out of the box, a best practice is to define a common message flow in its own be file which may be imported into other message flows. This approach however has some limitations: * It's input and output channels are referenced in every consuming flow. Each common flow must ensure unique channel names -* True encapsuation is impossible as any internal channels and components are exposed to the consuming flow. Note that these must have +* True encapsulation is impossible as any internal channels and components are exposed to the consuming flow. Note that these must have unique names as well * Since a common flow is statically bound to channels, it cannot be used in a chain without implementing some type of service-activator/ gateway wrapper.