[nifi] 12/18: NIFI-6142: Fixing some typos in user/dev guides

[jo...@apache.org]

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

joewitt pushed a commit to branch NIFI-6169-RC1
in repository https://gitbox.apache.org/repos/asf/nifi.git

commit 57d1aa2b5e3934fc058cb9834af573fd8794d9aa
Author: Peter Turcsanyi <tu...@cloudera.com>
AuthorDate: Fri Mar 22 14:32:31 2019 +0100

    NIFI-6142: Fixing some typos in user/dev guides
    
    Signed-off-by: Pierre Villard <pi...@gmail.com>
    
    This closes #3384.
---
 nifi-docs/src/main/asciidoc/developer-guide.adoc | 8 ++++----
 nifi-docs/src/main/asciidoc/user-guide.adoc      | 6 +++---
 2 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/nifi-docs/src/main/asciidoc/developer-guide.adoc b/nifi-docs/src/main/asciidoc/developer-guide.adoc
index 67c827b..541a5b1 100644
--- a/nifi-docs/src/main/asciidoc/developer-guide.adoc
+++ b/nifi-docs/src/main/asciidoc/developer-guide.adoc
@@ -75,7 +75,7 @@ high-level description of the most common extension points:
       that is most effective for a particular use case.
 
 - AuthorityProvider
-    * An AuthorityProvide is responsible for determining which privileges and roles, if any,
+    * An AuthorityProvider is responsible for determining which privileges and roles, if any,
       a given user should be granted.
 
 
@@ -601,7 +601,7 @@ A Processor, Controller Service, or Reporting Task can be marked with the @Restr
 will result in the component being treated as restricted and will require a user to be explicitly added to the
 list of users who can access restricted components. Once a user is permitted to access restricted components,
 they will be allowed to create and modify those components assuming all other permissions are permitted.
-Without access to restricted components, a user will be still be aware these types of components exist but will
+Without access to restricted components, a user will still be aware these types of components exist but will
 be unable to create or modify them even with otherwise sufficient permissions.
 
 [[state_manager]]
@@ -1321,7 +1321,7 @@ relationships for a given input FlowFile.
 Additionally, some Processors may need to "group" the data that is
 sent to each Relationship so that each FlowFile
 that is sent to a relationship has the same value. In our example, we
-may wan to allow the Regular Expression
+may want to allow the Regular Expression
 to have a Capturing Group and if two different lines in the CSV match
 the Regular Expression but have different
 values for the Capturing Group, we want them to be added to two
@@ -1415,7 +1415,7 @@ preferred
 to use the `clone(FlowFile, long, long)` method instead of the
 `create(FlowFile)` method of the ProcessSession. In this case, the
 offset
-of the original FlwoFile at which the new FlowFile's content should
+of the original FlowFile at which the new FlowFile's content should
 begin is passed as the second argument to the `clone` method. The
 length
 of the new FlowFile is passed as the third argument to the `clone`
diff --git a/nifi-docs/src/main/asciidoc/user-guide.adoc b/nifi-docs/src/main/asciidoc/user-guide.adoc
index 16863e5..81ea02e 100644
--- a/nifi-docs/src/main/asciidoc/user-guide.adoc
+++ b/nifi-docs/src/main/asciidoc/user-guide.adoc
@@ -162,7 +162,7 @@ used by DFMs to manage the flow, as well as by administrators who manage user ac
 and configure system properties, such as how many system resources should be provided to the application.
 
 On the right side of the canvas is Search, and the Global Menu. You can use Search to easily find components on the
-canvas and can to search by component name, type, identifier, configuration properties, and their values. The Global Menu
+canvas and to search by component name, type, identifier, configuration properties, and their values. The Global Menu
 contains options that allow you to manipulate existing components on the canvas:
 
 image::global-menu.png[NiFi Global Menu]
@@ -195,7 +195,7 @@ The available global access policies are:
 components may indicate which specific permissions are required. Permissions can be granted for specific restrictions or be granted regardless
 of restrictions. If permission is granted regardless of restrictions, the user can create/modify all restricted components.
 |access all policies   |Allows users to view and modify the policies for all components
-|access users/groups   |Allows users view and modify the users and user groups
+|access users/groups   |Allows users to view and modify the users and user groups
 |retrieve site-to-site details | Allows other NiFi instances to retrieve Site-To-Site details
 |view system diagnostics  |Allows users to view System Diagnostics
 |proxy user requests  |Allows proxy machines to send requests on the behalf of others
@@ -301,7 +301,7 @@ While the options available from the context menu vary, the following options ar
 NOTE: For Processors, Ports, Remote Process Groups, Connections and Labels, it is possible to open the configuration dialog by double-clicking on desired component.
 
 - *Start* or *Stop*: This option allows the user to start or stop a Processor; the option will be either Start or Stop, depending on the current state of the Processor.
-- *Enable* or *Disable*: This option allows the user to enable or enable a Processor; the option will be either Enable or Disable, depending on the current state of the Processor.
+- *Enable* or *Disable*: This option allows the user to enable or disable a Processor; the option will be either Enable or Disable, depending on the current state of the Processor.
 - *View data provenance*: This option displays the NiFi Data Provenance table, with information about data provenance events for the FlowFiles routed through that Processor (see <<data_provenance>>).
 - *View status history*: This option opens a graphical representation of the Processor's statistical information over time.
 - *View usage*: This option takes the user to the Processor's usage documentation.