This is an automated email from the ASF dual-hosted git repository.
pvillard31 pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/nifi.git
The following commit(s) were added to refs/heads/main by this push:
new 9b525392b43 NIFI-16522 Fixed typos in documentation (#11861)
9b525392b43 is described below
commit 9b525392b4362723065b77e276d63e6532bdee22
Author: Anshu Singh <[email protected]>
AuthorDate: Wed Oct 28 20:17:27 2026 +0530
NIFI-16522 Fixed typos in documentation (#11861)
---
minifi/minifi-docs/src/main/markdown/System_Admin_Guide.md | 2 +-
.../src/main/markdown/minifi-java-agent-quick-start.md | 2 +-
nifi-docs/src/main/asciidoc/administration-guide.adoc | 10 +++++-----
nifi-docs/src/main/asciidoc/developer-guide.adoc | 2 +-
nifi-docs/src/main/asciidoc/getting-started.adoc | 2 +-
nifi-docs/src/main/asciidoc/python-developer-guide.adoc | 4 ++--
nifi-docs/src/main/asciidoc/record-path-guide.adoc | 2 +-
nifi-docs/src/main/asciidoc/toolkit-guide.adoc | 2 +-
nifi-docs/src/main/asciidoc/user-guide.adoc | 8 ++++----
nifi-docs/src/main/asciidoc/walkthroughs.adoc | 2 +-
.../additionalDetails.md | 2 +-
.../org.apache.nifi.jasn1.JASN1Reader/additionalDetails.md | 2 +-
.../additionalDetails.md | 2 +-
.../additionalDetails.md | 2 +-
.../additionalDetails.md | 2 +-
.../additionalDetails.md | 2 +-
.../additionalDetails.md | 2 +-
.../additionalDetails.md | 2 +-
.../additionalDetails.md | 2 +-
.../additionalDetails.md | 4 ++--
.../additionalDetails.md | 2 +-
.../additionalDetails.md | 2 +-
.../org.apache.nifi.json.JsonPathReader/additionalDetails.md | 2 +-
.../org.apache.nifi.json.JsonTreeReader/additionalDetails.md | 2 +-
.../docs/org.apache.nifi.xml.XMLReader/additionalDetails.md | 2 +-
.../additionalDetails.md | 2 +-
.../org.apache.nifi.yaml.YamlTreeReader/additionalDetails.md | 2 +-
.../additionalDetails.md | 2 +-
.../additionalDetails.md | 2 +-
nifi-frontend/src/main/frontend/README.md | 2 +-
nifi-frontend/src/main/frontend/apps/nifi-registry/README.md | 4 ++--
.../src/main/asciidoc/administration-guide.adoc | 4 ++--
.../nifi-registry-docs/src/main/asciidoc/user-guide.adoc | 2 +-
nifi-stateless/nifi-stateless-assembly/README.md | 10 +++++-----
34 files changed, 49 insertions(+), 49 deletions(-)
diff --git a/minifi/minifi-docs/src/main/markdown/System_Admin_Guide.md
b/minifi/minifi-docs/src/main/markdown/System_Admin_Guide.md
index 5b69c0701ac..2ebfee7d861 100644
--- a/minifi/minifi-docs/src/main/markdown/System_Admin_Guide.md
+++ b/minifi/minifi-docs/src/main/markdown/System_Admin_Guide.md
@@ -192,7 +192,7 @@ minifi.sh flowStatus
processor:TailFile:health,stats,bulletins
```
Currently the script only accepts one high level option at a time. Also any
names of connections, remote process groups, or processors that contain " " (a
space), ":", ";" or "," cause parsing errors when querying.
-**Note:** The examples in this documentation are provided for *nix based
environments. Windows support is also provided by by the
`flowstatus-minifi.bat` file. To perform one of the listed interactions,
`minifi.sh flowStatus` would simply be replaced by `flowstatus-minifi.bat`.
For example, the sample query above in *nix environments,
+**Note:** The examples in this documentation are provided for *nix based
environments. Windows support is also provided by the `flowstatus-minifi.bat`
file. To perform one of the listed interactions, `minifi.sh flowStatus` would
simply be replaced by `flowstatus-minifi.bat`. For example, the sample query
above in *nix environments,
```
minifi.sh flowStatus processor:TailFile:health,stats,bulletins
diff --git
a/minifi/minifi-docs/src/main/markdown/minifi-java-agent-quick-start.md
b/minifi/minifi-docs/src/main/markdown/minifi-java-agent-quick-start.md
index 84e1daa3465..ad606d90a25 100644
--- a/minifi/minifi-docs/src/main/markdown/minifi-java-agent-quick-start.md
+++ b/minifi/minifi-docs/src/main/markdown/minifi-java-agent-quick-start.md
@@ -143,7 +143,7 @@ To load a new dataflow for a MiNiFi instance to run:
2. When a new flow is available on the C2 server, MiNiFi will download it via
C2 and restart itself to pick up the changes
## C2 Heartbeat
-Heartbeat provides status(agent, flowm device) and operational capabilities to
C2 server(s)
+Heartbeat provides status(agent, flow, device) and operational capabilities to
C2 server(s)
### Agent manifest
The agent manifest is the descriptor of the available extensions. The size of
the heartbeat
diff --git a/nifi-docs/src/main/asciidoc/administration-guide.adoc
b/nifi-docs/src/main/asciidoc/administration-guide.adoc
index 8bde48a3c6f..0aafc7579b9 100644
--- a/nifi-docs/src/main/asciidoc/administration-guide.adoc
+++ b/nifi-docs/src/main/asciidoc/administration-guide.adoc
@@ -1637,7 +1637,7 @@ Component level access policies govern the following
component level authorizati
NOTE: You can apply access policies to all component types except connections.
Connection authorizations are inferred by the individual access policies on
the source and destination components of the connection, as well as the access
policy of the process group containing the components. This is discussed in
more detail in the <<creating-a-connection>> and <<editing-a-connection>>
examples below.
-NOTE: In order to access List Queue or Delete Queue for a connection, a user
requires permission to the "view the data" and "modify the data" policies on
the component. In a clustered environment, all nodes must be be added to these
policies as well, as a user request could be replicated through any node in the
cluster.
+NOTE: In order to access List Queue or Delete Queue for a connection, a user
requires permission to the "view the data" and "modify the data" policies on
the component. In a clustered environment, all nodes must be added to these
policies as well, as a user request could be replicated through any node in the
cluster.
[[access-policy-inheritance]]
===== Access Policy Inheritance
@@ -2713,7 +2713,7 @@ _true_. Once Netty is enabled, you should see log
messages like the following in
=== Embedded ZooKeeper with TLS
-A NiFi cluster can be deployed using a ZooKeeper instance(s) embedded in NiFi
itself which all nodes can communicate with. As of NiFi 1.13.0, communication
between nodes and this embedded ZooKeeper can now be secured with TLS. Versions
of NiFi prior to 1.13 did not use secure client access with embedded
ZooKeeper(s). The configuration for the client side of the connection will
operate in the same way as an external ZooKeeper. That is, it will use the
`+nifi.security.*+` properties from t [...]
+A NiFi cluster can be deployed using a ZooKeeper instance(s) embedded in NiFi
itself which all nodes can communicate with. As of NiFi 1.13.0, communication
between nodes and this embedded ZooKeeper can now be secured with TLS. Versions
of NiFi prior to 1.13 did not use secure client access with embedded
ZooKeeper(s). The configuration for the client side of the connection will
operate in the same way as an external ZooKeeper. That is, it will use the
`+nifi.security.*+` properties from t [...]
The server configuration will operate in the same way as an insecure embedded
server, but with the `+secureClientPort+` set (typically port `+2281+`).
@@ -3237,7 +3237,7 @@ may increase the rate at which the Provenance Repository
is able to process thes
|`nifi.provenance.repository.always.sync`|If set to `true`, any change to the
repository will be synchronized to the disk, meaning that NiFi will ask the
operating system not to cache the information. This is very expensive and can
significantly reduce NiFi performance. However, if it is `false`, there could
be the potential for data loss if either there is a sudden power loss or the
operating system crashes. The default value is `false`.
|`nifi.provenance.repository.journal.count`|The number of journal files that
should be used to serialize Provenance Event data. Increasing this value will
allow more tasks to simultaneously update the repository but will result in
more expensive merging of the journal files later. This value should ideally be
equal to the number of threads that are expected to update the repository
simultaneously, but 16 tends to work well in must environments. The default
value is `16`.
|`nifi.provenance.repository.indexed.fields`|This is a comma-separated list of
the fields that should be indexed and made searchable. Fields that are not
indexed will not be searchable. Valid fields are: `EventType`, `FlowFileUUID`,
`Filename`, `TransitURI`, `ProcessorID`, `AlternateIdentifierURI`,
`Relationship`, `Details`. The default value is: `EventType, FlowFileUUID,
Filename, ProcessorID`.
-|`nifi.provenance.repository.indexed.attributes`|This is a comma-separated
list of FlowFile Attributes that should be indexed and made searchable. It is
blank by default. But some good examples to consider are `filename`, `uuid`,
and `mime.type` as well as any custom attritubes you might use which are
valuable for your use case.
+|`nifi.provenance.repository.indexed.attributes`|This is a comma-separated
list of FlowFile Attributes that should be indexed and made searchable. It is
blank by default. But some good examples to consider are `filename`, `uuid`,
and `mime.type` as well as any custom attributes you might use which are
valuable for your use case.
|`nifi.provenance.repository.index.shard.size`|Large values for the shard size
will result in more Java heap usage when searching the Provenance Repository
but should provide better performance. The default value is `500 MB`.
|`nifi.provenance.repository.max.attribute.length`|Indicates the maximum
length that a FlowFile attribute can be when retrieving a Provenance Event from
the repository. If the length of any attribute exceeds this value, it will be
truncated when the event is retrieved. The default value is `65536`.
|====
@@ -3791,7 +3791,7 @@ for storing data. Each 'directory' in this structure is
referred to as a ZNode.
that should be used for storing data. The default value is `/nifi`. This is
important to set correctly, as which cluster
the NiFi instance attempts to join is determined by which ZooKeeper instance
it connects to and the ZooKeeper Root Node
that is specified.
-|`nifi.zookeeper.client.secure`|Whether to acccess ZooKeeper using client TLS.
The default value is `false`.
+|`nifi.zookeeper.client.secure`|Whether to access ZooKeeper using client TLS.
The default value is `false`.
|`nifi.zookeeper.security.keystore`|Filename of the Keystore containing the
private key to use when communicating with ZooKeeper.
|`nifi.zookeeper.security.keystoreType`|Optional. The type of the Keystore.
Must be `PKCS12`, `JKS`, or `PEM`. If not specified the type will be determined
from the file extension (`.p12`, `.jks`, `.pem`).
|`nifi.zookeeper.security.keystorePasswd`|The password for the Keystore.
@@ -4235,7 +4235,7 @@ The `nifi.nar.library.directory` is used for the default
location for provided N
nifi.nar.library.directory=./lib
-The `nifi.nar.library.directory.<custom>` allows the admin to provide multiple
arbritary paths for NiFi to locate custom processors. A unique property
identifier must append the property for each unique path. For example:
+The `nifi.nar.library.directory.<custom>` allows the admin to provide multiple
arbitrary paths for NiFi to locate custom processors. A unique property
identifier must append the property for each unique path. For example:
nifi.nar.library.directory.myCustomLibs=./my-custom-nars/lib
nifi.nar.library.directory.otherCustomLibs=./other-custom-nars/lib
diff --git a/nifi-docs/src/main/asciidoc/developer-guide.adoc
b/nifi-docs/src/main/asciidoc/developer-guide.adoc
index b3637a9da39..8e9fc0ea3b6 100644
--- a/nifi-docs/src/main/asciidoc/developer-guide.adoc
+++ b/nifi-docs/src/main/asciidoc/developer-guide.adoc
@@ -386,7 +386,7 @@ In addition, if a property is dependent on another property
(by means of the `Pr
For example, consider the following two Property Descriptors:
```
-PropertyDescriptor USE_FILE = new PropertyDescriptor.Buildler()
+PropertyDescriptor USE_FILE = new PropertyDescriptor.Builder()
.name("Use File")
.displayName("Use File")
.required(true)
diff --git a/nifi-docs/src/main/asciidoc/getting-started.adoc
b/nifi-docs/src/main/asciidoc/getting-started.adoc
index d49c2105da8..a6819e6c1ab 100644
--- a/nifi-docs/src/main/asciidoc/getting-started.adoc
+++ b/nifi-docs/src/main/asciidoc/getting-started.adoc
@@ -344,7 +344,7 @@ categorizing them by their functions.
and the system call is expected to receive no input. In order to
provide input to the process, use the ExecuteStreamCommand Processor.
- *ExecuteStreamCommand*: Runs the user-defined Operating System command. The
contents of the FlowFile are optionally streamed to the StdIn
- of the process. The content that is written to StdOut becomes the content of
hte outbound FlowFile. This Processor cannot be used a Source Processor -
+ of the process. The content that is written to StdOut becomes the content of
the outbound FlowFile. This Processor cannot be used a Source Processor -
it must be fed incoming FlowFiles in order to perform its work. To
perform the same type of functionality with a Source Processor, see the
ExecuteProcess Processor.
diff --git a/nifi-docs/src/main/asciidoc/python-developer-guide.adoc
b/nifi-docs/src/main/asciidoc/python-developer-guide.adoc
index 7cc401a35bc..c004fd81197 100644
--- a/nifi-docs/src/main/asciidoc/python-developer-guide.adoc
+++ b/nifi-docs/src/main/asciidoc/python-developer-guide.adoc
@@ -199,7 +199,7 @@ expression and then get the String representation of the
value.
The FlowFile is a proxy to the Java `InputFlowFile` object. This exposes the
following methods:
-`getContentsAsBytes` : returns the contents of the FlowFile as a byte array.
This method should be used conservatively, as it it loads entire contents
+`getContentsAsBytes` : returns the contents of the FlowFile as a byte array.
This method should be used conservatively, as it loads entire contents
of the FlowFile into a byte array on the Java side, and then sends a copy to
the Python side. As a result, the FlowFile's contents are buffered into memory
twice, once on the Java heap and once in the Python process.
@@ -511,7 +511,7 @@ Any relationship returned by `getRelationships` appears
besides the `success` re
As noted above, the `ProcessorDetails` and `Java` inner classes are important
to Processors. The `Java` inner class must be defined
on all Processors and must include a member named `implements` that is a list
of Java interfaces that the class implements. This is
-important, as it allows the Py4J protocol to understand how to interact with
this obect from the Java side.
+important, as it allows the Py4J protocol to understand how to interact with
this object from the Java side.
The `ProcessorDetails` class tells NiFi about the Processor so that it can
allow configuration of the Processor seamlessly through the NiFi UI.
Additionally, it provides details about what is necessary in order to use the
Processor.
diff --git a/nifi-docs/src/main/asciidoc/record-path-guide.adoc
b/nifi-docs/src/main/asciidoc/record-path-guide.adoc
index 0abf0210cd7..de45f9fa757 100644
--- a/nifi-docs/src/main/asciidoc/record-path-guide.adoc
+++ b/nifi-docs/src/main/asciidoc/record-path-guide.adoc
@@ -501,7 +501,7 @@ Additionally, this can be used in conjunction with arrays.
For example, if we ha
}
----
-We can evaluate hte following Record paths:
+We can evaluate the following Record paths:
|==========================================================
| RecordPath | Return value
diff --git a/nifi-docs/src/main/asciidoc/toolkit-guide.adoc
b/nifi-docs/src/main/asciidoc/toolkit-guide.adoc
index 581591119e6..52264194145 100644
--- a/nifi-docs/src/main/asciidoc/toolkit-guide.adoc
+++ b/nifi-docs/src/main/asciidoc/toolkit-guide.adoc
@@ -38,7 +38,7 @@ When executing either the Notify or Node Manager tools in a
secured environment
[[nifi_CLI]]
== NiFi CLI
-This tool offers a CLI focused on interacting with NiFi and NiFi Registry in
order to automate tasks, such as deploying flows from a NIFi Registy to a NiFi
instance or managing process groups and cluster nodes.
+This tool offers a CLI focused on interacting with NiFi and NiFi Registry in
order to automate tasks, such as deploying flows from a NIFi Registry to a NiFi
instance or managing process groups and cluster nodes.
=== Usage
The CLI toolkit can be executed in standalone mode to execute a single
command, or interactive mode to enter an interactive shell.
diff --git a/nifi-docs/src/main/asciidoc/user-guide.adoc
b/nifi-docs/src/main/asciidoc/user-guide.adoc
index 3790d4043d1..f6c8046e33a 100644
--- a/nifi-docs/src/main/asciidoc/user-guide.adoc
+++ b/nifi-docs/src/main/asciidoc/user-guide.adoc
@@ -768,7 +768,7 @@ FlowFile Concurrency is used to control how data is brought
into the Process Gro
When the FlowFile Concurrency is set to "Unbounded", the Input Ports in the
Process Group will ingest data as quickly as they
are able, provided that back pressure does not prevent them from doing so.
-When the FlowFile Concurrency is configured to "Single FlowFile Per Node", the
Input Ports will only allow a single FlowFile through at at time.
+When the FlowFile Concurrency is configured to "Single FlowFile Per Node", the
Input Ports will only allow a single FlowFile through at a time.
Once that FlowFile enters the Process Group, no additional FlowFiles will be
brought in until all FlowFiles have left the Process Group (either by
being removed from the system/auto-terminated, or by exiting through an Output
Port). This will often result in slower performance, as it reduces
the parallelization that NiFi uses to process the data. However, there are
several reasons that a user may want to use this approach. A common use case
@@ -1882,7 +1882,7 @@ As a result, it is recommended to keep Stateless flows to
a single source and a
==== Use Caution When Merging
Because each concurrent task runs a separate copy of the Stateless flow, it is
important to keep in mind that the minimum number of incoming FlowFiles needed
for a merge (via MergeContent
-or MergeRecord, for example) may increase by a multiple of the number of
concurrent tasks. As such, it may take a significant amount of time for that
that much data to queue up.
+or MergeRecord, for example) may increase by a multiple of the number of
concurrent tasks. As such, it may take a significant amount of time for that
much data to queue up.
Additionally, the Stateless flow has a timeout to limit how long it can run.
Because of this, it is important to use caution when configuring limits for
these types of Processors.
It is always advisable to set a Max Bin Age less than the timeout of the
Stateless flow in order to ensure that the dataflow doesn't continually
timeout. While it is true that continually
@@ -2733,7 +2733,7 @@ The version of the flow is changed:
image::flow-version-changed.png["Flow Version Changed"]
-In the example shown, the versioned flow is upgraded from an older to the
newer latest version. However, a versioned flow can also be rollbacked to an
older version.
+In the example shown, the versioned flow is upgraded from an older to the
newer latest version. However, a versioned flow can also be rolled back to an
older version.
NOTE: For "Change version" to be an available selection, local changes to the
process group need to be reverted.
@@ -3096,7 +3096,7 @@ dataflow that will fix the problem.
Select Node Status History to view instance-specific metrics from the last 24
hours or longer if the status repository implementation
supports it. If the instance runs for less than the maximum configured time,
then metrics will be available for the period of time
since it has been started. The status history can help the DFM in
troubleshooting performance issues and provides a general
-view on the health of the node. The status history includes information about
the memory and disk usage, CPU utilzation and garbage collection.
+view on the health of the node. The status history includes information about
the memory and disk usage, CPU utilization and garbage collection.
Two other tools in the Global Menu are Controller Settings and Users. The
Controller Settings page provides the ability to set the maximum number of
threads that are available
to the application. It also provides tabs where DFMs may add and configure
<<Controller_Services>> and <<Reporting_Tasks>>. The Users page is used to
manage user access, which is described in
diff --git a/nifi-docs/src/main/asciidoc/walkthroughs.adoc
b/nifi-docs/src/main/asciidoc/walkthroughs.adoc
index 02a5e5217c1..3956e49bee5 100644
--- a/nifi-docs/src/main/asciidoc/walkthroughs.adoc
+++ b/nifi-docs/src/main/asciidoc/walkthroughs.adoc
@@ -214,7 +214,7 @@ NOTE: Setting a port between 1 - 1024 requires `root`
access on *nix systems
Apache NiFi requires
link:https://en.wikipedia.org/wiki/Transport_Layer_Security[Transport Layer
Security (TLS)^] configuration for multiple reasons.
-. To encrypt communication between clients and server (this provides
confidentialty and integrity over transmitted data)
+. To encrypt communication between clients and server (this provides
confidentiality and integrity over transmitted data)
. To prevent malicious users from intercepting data or impersonating the server
. To enable any authentication & authorization mechanisms
diff --git
a/nifi-extension-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/resources/docs/org.apache.nifi.amqp.processors.ConsumeAMQP/additionalDetails.md
b/nifi-extension-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/resources/docs/org.apache.nifi.amqp.processors.ConsumeAMQP/additionalDetails.md
index 3990a1379d2..eb7d565a065 100644
---
a/nifi-extension-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/resources/docs/org.apache.nifi.amqp.processors.ConsumeAMQP/additionalDetails.md
+++
b/nifi-extension-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/resources/docs/org.apache.nifi.amqp.processors.ConsumeAMQP/additionalDetails.md
@@ -26,7 +26,7 @@ may also help you to brush up on some of the AMQP basics.
This processor does two things. It constructs FlwFile by extracting
information from the consumed AMQP message (both
body and attributes). Once message is consumed a FlowFile is constructed. The
message body is written to a FlowFile and
-its _com.rabbitmq.client.AMQP.BasicProperties_ are transfered into the
FlowFile as attributes. AMQP attribute names are
+its _com.rabbitmq.client.AMQP.BasicProperties_ are transferred into the
FlowFile as attributes. AMQP attribute names are
prefixed with _amqp$_ prefix.
## AMQP Properties
diff --git
a/nifi-extension-bundles/nifi-asn1-bundle/nifi-asn1-services/src/main/resources/docs/org.apache.nifi.jasn1.JASN1Reader/additionalDetails.md
b/nifi-extension-bundles/nifi-asn1-bundle/nifi-asn1-services/src/main/resources/docs/org.apache.nifi.jasn1.JASN1Reader/additionalDetails.md
index d0380aa1c70..c07d98a4301 100644
---
a/nifi-extension-bundles/nifi-asn1-bundle/nifi-asn1-services/src/main/resources/docs/org.apache.nifi.jasn1.JASN1Reader/additionalDetails.md
+++
b/nifi-extension-bundles/nifi-asn1-bundle/nifi-asn1-services/src/main/resources/docs/org.apache.nifi.jasn1.JASN1Reader/additionalDetails.md
@@ -29,7 +29,7 @@ per usual - will show error messages related to the failure
but interpreting tho
For help troubleshooting such messages please refer to the _Troubleshooting_
section below.**
The root model type can be defined via the _Root Model Name_ property. It's
format should be "MODULE-NAME.ModelType".
-"MODULE-NAME" is the name of the ASN module defined at the beginnig of the ASN
schema file. "ModelType" is an ASN type
+"MODULE-NAME" is the name of the ASN module defined at the beginning of the
ASN schema file. "ModelType" is an ASN type
defined in the ASN files that is not referenced by any other type. The reader
created by this service expects ASN
records of this root model type.
diff --git
a/nifi-extension-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/resources/docs/org.apache.nifi.processors.aws.dynamodb.PutDynamoDBRecord/additionalDetails.md
b/nifi-extension-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/resources/docs/org.apache.nifi.processors.aws.dynamodb.PutDynamoDBRecord/additionalDetails.md
index e9fd064f9af..88a6bbe5b7c 100644
---
a/nifi-extension-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/resources/docs/org.apache.nifi.processors.aws.dynamodb.PutDynamoDBRecord/additionalDetails.md
+++
b/nifi-extension-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/resources/docs/org.apache.nifi.processors.aws.dynamodb.PutDynamoDBRecord/additionalDetails.md
@@ -35,7 +35,7 @@ Some conversions and simplifications are necessary during
inserting the data. Th
* Internal record structures are converted into maps.
* Choice is not a supported data type, regardless of the actual wrapped data
type, values enveloped in Choice are
handled as Strings.
-* Unknown data types are handled as stings.
+* Unknown data types are handled as strings.
## Limitations
diff --git
a/nifi-extension-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/resources/docs/org.apache.nifi.processors.aws.ml.textract.GetAwsTextractJobStatus/additionalDetails.md
b/nifi-extension-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/resources/docs/org.apache.nifi.processors.aws.ml.textract.GetAwsTextractJobStatus/additionalDetails.md
index c5bc24563b5..1deda50cb92 100644
---
a/nifi-extension-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/resources/docs/org.apache.nifi.processors.aws.ml.textract.GetAwsTextractJobStatus/additionalDetails.md
+++
b/nifi-extension-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/resources/docs/org.apache.nifi.processors.aws.ml.textract.GetAwsTextractJobStatus/additionalDetails.md
@@ -24,5 +24,5 @@ forms and tables.
### Usage
GetAwsTextractJobStatus Processor is designed to periodically check textract
job status. This processor should be used
-in pair with StartAwsTextractJob Processor. FlowFile will contain the
serialized Tetract response that contains the
+in pair with StartAwsTextractJob Processor. FlowFile will contain the
serialized Textract response that contains the
result and additional metadata as it is documented in AWS Textract Reference.
\ No newline at end of file
diff --git
a/nifi-extension-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/resources/docs/org.apache.nifi.processors.aws.ml.textract.StartAwsTextractJob/additionalDetails.md
b/nifi-extension-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/resources/docs/org.apache.nifi.processors.aws.ml.textract.StartAwsTextractJob/additionalDetails.md
index 6c93a51f4b2..4297957085d 100644
---
a/nifi-extension-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/resources/docs/org.apache.nifi.processors.aws.ml.textract.StartAwsTextractJob/additionalDetails.md
+++
b/nifi-extension-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/resources/docs/org.apache.nifi.processors.aws.ml.textract.StartAwsTextractJob/additionalDetails.md
@@ -32,7 +32,7 @@ higher precedence. After the job is triggered the serialized
json response will
awsTaskId attribute will be populated, so it makes it easier to query job
status by the corresponding get job status
processor.
-Three different type of textract task are supported: Documnet Analysis, Text
Detection, Expense Analysis.
+Three different type of textract task are supported: Document Analysis, Text
Detection, Expense Analysis.
### DocumentAnalysis
diff --git
a/nifi-extension-bundles/nifi-graph-bundle/nifi-other-graph-services/src/main/resources/docs/org.apache.nifi.graph.TinkerpopClientService/additionalDetails.md
b/nifi-extension-bundles/nifi-graph-bundle/nifi-other-graph-services/src/main/resources/docs/org.apache.nifi.graph.TinkerpopClientService/additionalDetails.md
index cdfbf14b0a4..286d9017223 100644
---
a/nifi-extension-bundles/nifi-graph-bundle/nifi-other-graph-services/src/main/resources/docs/org.apache.nifi.graph.TinkerpopClientService/additionalDetails.md
+++
b/nifi-extension-bundles/nifi-graph-bundle/nifi-other-graph-services/src/main/resources/docs/org.apache.nifi.graph.TinkerpopClientService/additionalDetails.md
@@ -21,7 +21,7 @@ This client service configures a connection to a Gremlin
Server and allows Greml
Gremlin Server. For more information on Gremlin and Gremlin Server, see
the [Apache Tinkerpop](http://tinkerpop.apache.org/) project.
-This client service supports two differnt modes of operation: Script
Submission and Bytecode Submission, described
+This client service supports two different modes of operation: Script
Submission and Bytecode Submission, described
below.
## Script Submission
diff --git
a/nifi-extension-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/resources/docs/org.apache.nifi.processors.hadoop.PutHDFS/additionalDetails.md
b/nifi-extension-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/resources/docs/org.apache.nifi.processors.hadoop.PutHDFS/additionalDetails.md
index ccac5dc65c4..dc6b41c7a64 100644
---
a/nifi-extension-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/resources/docs/org.apache.nifi.processors.hadoop.PutHDFS/additionalDetails.md
+++
b/nifi-extension-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/resources/docs/org.apache.nifi.processors.hadoop.PutHDFS/additionalDetails.md
@@ -54,7 +54,7 @@ ssl-client.xml Example:
</configuration>
```
-6. put 'ssl-client.xml' to the location looked up in the classpath, like under
NiFi conriguration directory.
+6. put 'ssl-client.xml' to the location looked up in the classpath, like under
NiFi configuration directory.
7. set the name of 'ssl-client.xml' to _hadoop.ssl.client.conf_ in the
'core-site.xml' which HDFS processors use.
```xml
diff --git
a/nifi-extension-bundles/nifi-mongodb-bundle/nifi-mongodb-processors/src/main/resources/docs/org.apache.nifi.processors.mongodb.GetMongo/additionalDetails.md
b/nifi-extension-bundles/nifi-mongodb-bundle/nifi-mongodb-processors/src/main/resources/docs/org.apache.nifi.processors.mongodb.GetMongo/additionalDetails.md
index ac6c5f2797f..4472a1f056c 100644
---
a/nifi-extension-bundles/nifi-mongodb-bundle/nifi-mongodb-processors/src/main/resources/docs/org.apache.nifi.processors.mongodb.GetMongo/additionalDetails.md
+++
b/nifi-extension-bundles/nifi-mongodb-bundle/nifi-mongodb-processors/src/main/resources/docs/org.apache.nifi.processors.mongodb.GetMongo/additionalDetails.md
@@ -37,7 +37,7 @@ The following options for limiting/shaping results are
available:
* Limit - limit the number of results. This should not be confused with the
"batch size" option which is a setting for
the underlying MongoDB driver to tell it how many items to retrieve in each
poll of the server.
* Sort - sort the result set. Requires a JSON document like _{ "someDate": -1
}_
-* Projection - control which fields to return. Exampe, which would remove
_\_id_: _{ "\_id": 0 }_
+* Projection - control which fields to return. Example, which would remove
_\_id_: _{ "\_id": 0 }_
## Misc Options
diff --git
a/nifi-extension-bundles/nifi-mongodb-bundle/nifi-mongodb-processors/src/main/resources/docs/org.apache.nifi.processors.mongodb.GetMongoRecord/additionalDetails.md
b/nifi-extension-bundles/nifi-mongodb-bundle/nifi-mongodb-processors/src/main/resources/docs/org.apache.nifi.processors.mongodb.GetMongoRecord/additionalDetails.md
index 7a53f561e6d..eaa2a0211b5 100644
---
a/nifi-extension-bundles/nifi-mongodb-bundle/nifi-mongodb-processors/src/main/resources/docs/org.apache.nifi.processors.mongodb.GetMongoRecord/additionalDetails.md
+++
b/nifi-extension-bundles/nifi-mongodb-bundle/nifi-mongodb-processors/src/main/resources/docs/org.apache.nifi.processors.mongodb.GetMongoRecord/additionalDetails.md
@@ -37,7 +37,7 @@ The following options for limiting/shaping results are
available:
* Limit - limit the number of results. This should not be confused with the
"batch size" option which is a setting for
the underlying MongoDB driver to tell it how many items to retrieve in each
poll of the server.
* Sort - sort the result set. Requires a JSON document like _{ "someDate": -1
}_
-* Projection - control which fields to return. Exampe, which would remove
_\_id_: _{ "\_id": 0 }_
+* Projection - control which fields to return. Example, which would remove
_\_id_: _{ "\_id": 0 }_
## Misc Options
diff --git
a/nifi-extension-bundles/nifi-scripting-bundle/nifi-scripting-processors/src/main/resources/docs/org.apache.nifi.processors.script.ScriptedValidateRecord/additionalDetails.md
b/nifi-extension-bundles/nifi-scripting-bundle/nifi-scripting-processors/src/main/resources/docs/org.apache.nifi.processors.script.ScriptedValidateRecord/additionalDetails.md
index c9cd212e266..0f45a8bbca7 100644
---
a/nifi-extension-bundles/nifi-scripting-bundle/nifi-scripting-processors/src/main/resources/docs/org.apache.nifi.processors.script.ScriptedValidateRecord/additionalDetails.md
+++
b/nifi-extension-bundles/nifi-scripting-bundle/nifi-scripting-processors/src/main/resources/docs/org.apache.nifi.processors.script.ScriptedValidateRecord/additionalDetails.md
@@ -17,7 +17,7 @@
### Description
-The ScriptedValidateRecord Processor provides the ability to use a scripting
language, such as Groovy or Jyton in order
+The ScriptedValidateRecord Processor provides the ability to use a scripting
language, such as Groovy or Jython in order
to validate Records in an incoming FlowFile. The provided script will be
evaluated against each Record in an incoming
FlowFile. Each of those records will then be routed to either the "valid" or
"invalid" FlowFile. As a result, each
incoming FlowFile may be broken up into two individual FlowFiles (if some
records are valid and some are invalid,
@@ -96,7 +96,7 @@ return recordIndex < 2 ? true : false
### Validating based on Record contents
The following script will filter the Records based on their content. Any
Records satisfies the condition will be part of
-the FlowFile routed to the `valid` Relationship, others wil lbe routed to the
`invalid` Relationship.
+the FlowFile routed to the `valid` Relationship, others will lbe routed to the
`invalid` Relationship.
Example Input (JSON):
diff --git
a/nifi-extension-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/resources/docs/org.apache.nifi.processors.standard.ExecuteStreamCommand/additionalDetails.md
b/nifi-extension-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/resources/docs/org.apache.nifi.processors.standard.ExecuteStreamCommand/additionalDetails.md
index a4e60dd4808..dbb1b4509de 100644
---
a/nifi-extension-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/resources/docs/org.apache.nifi.processors.standard.ExecuteStreamCommand/additionalDetails.md
+++
b/nifi-extension-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/resources/docs/org.apache.nifi.processors.standard.ExecuteStreamCommand/additionalDetails.md
@@ -68,7 +68,7 @@ environment variable that doesn't match the pattern
'command.argument.<commandIn
Consider that we want to execute a Maven command with the processor. If there
are multiple Java versions installed on
the system, you can specify which version will be used by setting the
`JAVA_HOME` environment variable. The output
-FlowFile will looke like this if we run `mvn` command with `--version`
argument:
+FlowFile will look like this if we run `mvn` command with `--version` argument:
```
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
diff --git
a/nifi-extension-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/resources/docs/org.apache.nifi.processors.standard.QueryRecord/additionalDetails.md
b/nifi-extension-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/resources/docs/org.apache.nifi.processors.standard.QueryRecord/additionalDetails.md
index 93972bf7032..ed619219140 100644
---
a/nifi-extension-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/resources/docs/org.apache.nifi.processors.standard.QueryRecord/additionalDetails.md
+++
b/nifi-extension-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/resources/docs/org.apache.nifi.processors.standard.QueryRecord/additionalDetails.md
@@ -142,7 +142,7 @@ WHERE RPATH(addresses, '/state[/label = ''home'']') <>
RPATH(addresses, '/state[
To explain this query in English, we can say that it selects the "title" and
"name" fields from any Record in the
FlowFile for which there is an address whose "label" is "home" and another
address whose "label" is "work" and for which
-the two addreses have different states.
+the two addresses have different states.
Similarly, we could select the entire Record (all fields) of any person who
has a "project" whose maintainer is the
Apache Software Foundation using the query:
diff --git
a/nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.json.JsonPathReader/additionalDetails.md
b/nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.json.JsonPathReader/additionalDetails.md
index a4071d0080c..0965f638f02 100644
---
a/nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.json.JsonPathReader/additionalDetails.md
+++
b/nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.json.JsonPathReader/additionalDetails.md
@@ -114,7 +114,7 @@ inference logic:
RECORD, ARRAY, and CHOICE.
* If two values are encountered for the same field in two different records
(or two values are encountered for an ARRAY
type), but neither value is of a type that is wider than the other, then a
CHOICE type is used. In the example above,
- the "values" field will be inferred as a CHOICE between a STRING or an
ARRRAY<STRING>.
+ the "values" field will be inferred as a CHOICE between a STRING or an
ARRAY<STRING>.
* If the "Time Format," "Timestamp Format," or "Date Format" properties are
configured, any value that would otherwise
be considered a STRING type is first checked against the configured formats
to see if it matches any of them. If the
value matches the Timestamp Format, the value is considered a Timestamp
field. If it matches the Date Format, it is
diff --git
a/nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.json.JsonTreeReader/additionalDetails.md
b/nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.json.JsonTreeReader/additionalDetails.md
index 88bba0a7639..eedc11c523b 100644
---
a/nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.json.JsonTreeReader/additionalDetails.md
+++
b/nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.json.JsonTreeReader/additionalDetails.md
@@ -104,7 +104,7 @@ inference logic:
RECORD, ARRAY, and CHOICE.
* If two values are encountered for the same field in two different records
(or two values are encountered for an ARRAY
type), but neither value is of a type that is wider than the other, then a
CHOICE type is used. In the example above,
- the "values" field will be inferred as a CHOICE between a STRING or an
ARRRAY<STRING>.
+ the "values" field will be inferred as a CHOICE between a STRING or an
ARRAY<STRING>.
* If the "Time Format," "Timestamp Format," or "Date Format" properties are
configured, any value that would otherwise
be considered a STRING type is first checked against the configured formats
to see if it matches any of them. If the
value matches the Timestamp Format, the value is considered a Timestamp
field. If it matches the Date Format, it is
diff --git
a/nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.xml.XMLReader/additionalDetails.md
b/nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.xml.XMLReader/additionalDetails.md
index 019db33aeb3..d7e3c8f985f 100755
---
a/nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.xml.XMLReader/additionalDetails.md
+++
b/nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.xml.XMLReader/additionalDetails.md
@@ -679,7 +679,7 @@ inference logic:
RECORD, ARRAY, and CHOICE.
* If two values are encountered for the same field in two different records
(or two values are encountered for an ARRAY
type), but neither value is of a type that is wider than the other, then a
CHOICE type is used. In the example above,
- the "values" field will be inferred as a CHOICE between a STRING or an
ARRRAY<STRING>.
+ the "values" field will be inferred as a CHOICE between a STRING or an
ARRAY<STRING>.
* If the "Time Format," "Timestamp Format," or "Date Format" properties are
configured, any value that would otherwise
be considered a STRING type is first checked against the configured formats
to see if it matches any of them. If the
value matches the Timestamp Format, the value is considered a Timestamp
field. If it matches the Date Format, it is
diff --git
a/nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.xml.XMLRecordSetWriter/additionalDetails.md
b/nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.xml.XMLRecordSetWriter/additionalDetails.md
index ea6008b63f1..0994b5e25ea 100755
---
a/nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.xml.XMLRecordSetWriter/additionalDetails.md
+++
b/nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.xml.XMLRecordSetWriter/additionalDetails.md
@@ -87,7 +87,7 @@ RecordSet (
```
If the writer is configured always to suppress missing or null values, only
the field of name "name1" will appear in the
-XML. If the writer ist configured only to suppress missing values, the field
of name "name2" will appear in the XML as a
+XML. If the writer is configured only to suppress missing values, the field of
name "name2" will appear in the XML as a
node without content for the first record. If the writer is configured never
to suppress anything, the field of name "
name2" will appear in the XML as a node without content for both records.
diff --git
a/nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.yaml.YamlTreeReader/additionalDetails.md
b/nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.yaml.YamlTreeReader/additionalDetails.md
index 2bcd33d2581..c2c4bcd947e 100644
---
a/nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.yaml.YamlTreeReader/additionalDetails.md
+++
b/nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.yaml.YamlTreeReader/additionalDetails.md
@@ -104,7 +104,7 @@ inference logic:
RECORD, ARRAY, and CHOICE.
* If two values are encountered for the same field in two different records
(or two values are encountered for an ARRAY
type), but neither value is of a type that is wider than the other, then a
CHOICE type is used. In the example above,
- the "values" field will be inferred as a CHOICE between a STRING or an
ARRRAY<STRING>.
+ the "values" field will be inferred as a CHOICE between a STRING or an
ARRAY<STRING>.
* If the "Time Format," "Timestamp Format," or "Date Format" properties are
configured, any value that would otherwise
be considered a STRING type is first checked against the configured formats
to see if it matches any of them. If the
value matches the Timestamp Format, the value is considered a Timestamp
field. If it matches the Date Format, it is
diff --git
a/nifi-extension-bundles/nifi-update-attribute-bundle/nifi-update-attribute-processor/src/main/resources/docs/org.apache.nifi.processors.attributes.UpdateAttribute/additionalDetails.md
b/nifi-extension-bundles/nifi-update-attribute-bundle/nifi-update-attribute-processor/src/main/resources/docs/org.apache.nifi.processors.attributes.UpdateAttribute/additionalDetails.md
index 3f730b68b8a..29e96198355 100644
---
a/nifi-extension-bundles/nifi-update-attribute-bundle/nifi-update-attribute-processor/src/main/resources/docs/org.apache.nifi.processors.attributes.UpdateAttribute/additionalDetails.md
+++
b/nifi-extension-bundles/nifi-update-attribute-bundle/nifi-update-attribute-processor/src/main/resources/docs/org.apache.nifi.processors.attributes.UpdateAttribute/additionalDetails.md
@@ -115,7 +115,7 @@ Taken together, this rule says:
Continuing with this example, we can add another rule to check for files that
are larger than one gigabyte. When we add
this second rule, we can use the previous rule as a template, so to speak, by
taking advantage of the "Clone Rule" option
-in the menu for the Rule that you wan to clone. This will open with new Rule
form with the exisitng Rules criteria
+in the menu for the Rule that you wan to clone. This will open with new Rule
form with the existing Rules criteria
pre-populated.
In this example, the CheckForGiantFiles rule has these conditions:
diff --git
a/nifi-extension-bundles/nifi-websocket-bundle/nifi-websocket-processors/src/main/resources/docs/org.apache.nifi.processors.websocket.ConnectWebSocket/additionalDetails.md
b/nifi-extension-bundles/nifi-websocket-bundle/nifi-websocket-processors/src/main/resources/docs/org.apache.nifi.processors.websocket.ConnectWebSocket/additionalDetails.md
index 3a909df026c..60591553c83 100644
---
a/nifi-extension-bundles/nifi-websocket-bundle/nifi-websocket-processors/src/main/resources/docs/org.apache.nifi.processors.websocket.ConnectWebSocket/additionalDetails.md
+++
b/nifi-extension-bundles/nifi-websocket-bundle/nifi-websocket-processors/src/main/resources/docs/org.apache.nifi.processors.websocket.ConnectWebSocket/additionalDetails.md
@@ -31,7 +31,7 @@ with "header." and continue with they header key. For
example: "header.Authoriza
corresponding header value. If a new flowfile is passed to the processor, the
previous sessions will be closed, and any
data being sent will be aborted.
-1. header.Autorization | Basic base64UserNamePassWord
+1. header.Authorization | Basic base64UserNamePassWord
2. header.Content-Type | application, audio, example
For multiple header values provide a comma separated list.
\ No newline at end of file
diff --git a/nifi-frontend/src/main/frontend/README.md
b/nifi-frontend/src/main/frontend/README.md
index 2cff1beac4f..dda665ef096 100644
--- a/nifi-frontend/src/main/frontend/README.md
+++ b/nifi-frontend/src/main/frontend/README.md
@@ -3,7 +3,7 @@
## General Info
This module is the primary UI for NiFi. It contains the canvas and all UI's
for managing the NiFi instance. There are other modules within the codebase
-that support other UIs that intergate with this. These include documentation,
data viewers, advanced configuration UIs, error handling, and Registry UIs.
+that support other UIs that integrate with this. These include documentation,
data viewers, advanced configuration UIs, error handling, and Registry UIs.
Overtime, these will all be modernized and possibly brought into this Nx repo
to co-locate all the front end code.
## Source Structure
diff --git a/nifi-frontend/src/main/frontend/apps/nifi-registry/README.md
b/nifi-frontend/src/main/frontend/apps/nifi-registry/README.md
index fc3091a28bd..698e9b3237d 100644
--- a/nifi-frontend/src/main/frontend/apps/nifi-registry/README.md
+++ b/nifi-frontend/src/main/frontend/apps/nifi-registry/README.md
@@ -53,7 +53,7 @@ The NiFi Registry Server will need to know about the key
store, which has its ke
This will make the NiFi Registry available at https://localhost:18443.
-Now stop any running nifi registy you have running locally. In
nifi-registry/nifi-registry-assembly/target/nifi-registry-2.7.0-SNAPSHOT-bin/nifi-registry-2.7.0-SNAPSHOT/conf/
update the authorizers.xml and identity-providers.xml with the following:
+Now stop any running nifi registry you have running locally. In
nifi-registry/nifi-registry-assembly/target/nifi-registry-2.7.0-SNAPSHOT-bin/nifi-registry-2.7.0-SNAPSHOT/conf/
update the authorizers.xml and identity-providers.xml with the following:
### (authorizers.xml)
@@ -288,7 +288,7 @@ Now stop any running nifi registy you have running locally.
In nifi-registry/nif
</identityProviders>
```
-Now delete the users.xml file if you have onw. It will get recreated when you
restart the nifi registry backend.
+Now delete the users.xml file if you have one. It will get recreated when you
restart the nifi registry backend.
Next, update your
nifi-frontend/src/main/frontend/apps/nifi-registry/proxy.config.mjs so that
when you start your local frontend dev server it will proxy through to the
secured nifi registry backend:
diff --git
a/nifi-registry/nifi-registry-core/nifi-registry-docs/src/main/asciidoc/administration-guide.adoc
b/nifi-registry/nifi-registry-core/nifi-registry-docs/src/main/asciidoc/administration-guide.adoc
index d82cfd70d75..9b6d5eccd03 100644
---
a/nifi-registry/nifi-registry-core/nifi-registry-docs/src/main/asciidoc/administration-guide.adoc
+++
b/nifi-registry/nifi-registry-core/nifi-registry-docs/src/main/asciidoc/administration-guide.adoc
@@ -1576,7 +1576,7 @@ Qualified class name:
`org.apache.nifi.registry.provider.extension.FileSystemBun
==== S3BundlePersistenceProvider
-The `S3BundlePersistenceProvider` stores the content of extension bundles in a
AWS S3 bucket. The bucket is expected to already exist and be accessible to the
credentials provided to the persistence providcer.
+The `S3BundlePersistenceProvider` stores the content of extension bundles in a
AWS S3 bucket. The bucket is expected to already exist and be accessible to the
credentials provided to the persistence provider.
NOTE: This provider must be added to the classpath by specifying a custom
extension directory in _nifi-registry.properties_, such as
`nifi.registry.extension.dir.aws=./ext/aws/lib`, where `./ext/aws/` contains
the contents of the extracted _nifi-registry-aws-assembly-<version>-bin.zip_.
@@ -1604,7 +1604,7 @@ Qualified class name:
`org.apache.nifi.registry.aws.S3BundlePersistenceProvider`
|====
== Event Hooks
-Event hooks are an integration point that allows for custom code to to be
triggered when NiFi Registry application events occur.
+Event hooks are an integration point that allows for custom code to be
triggered when NiFi Registry application events occur.
[options="header,footer"]
|==================================================================================================================================================
diff --git
a/nifi-registry/nifi-registry-core/nifi-registry-docs/src/main/asciidoc/user-guide.adoc
b/nifi-registry/nifi-registry-core/nifi-registry-docs/src/main/asciidoc/user-guide.adoc
index 3bebba7ae3a..c5a45d62cb0 100644
---
a/nifi-registry/nifi-registry-core/nifi-registry-docs/src/main/asciidoc/user-guide.adoc
+++
b/nifi-registry/nifi-registry-core/nifi-registry-docs/src/main/asciidoc/user-guide.adoc
@@ -68,7 +68,7 @@ NOTE: The minimum recommended screen size is 1080px X 445px.
The NiFi Registry UI displays the shared resources available and provides
mechanisms for creating and administering users/groups, buckets and policies.
-When the application is started, the user is able to navigate to the UI by
going to the default address of `http://<hostname>:18080/nifi-registry` in a
web browser. There are no permissions configured by default, so anyone is able
to view and modify the flows and buckets. For information on securing the
system, see the
<<administration-guide.adocc#apache-nifi-registry-system-administrators-guide,System
Administrator’s Guide>>.
+When the application is started, the user is able to navigate to the UI by
going to the default address of `http://<hostname>:18080/nifi-registry` in a
web browser. There are no permissions configured by default, so anyone is able
to view and modify the flows and buckets. For information on securing the
system, see the
<<administration-guide.adoc#apache-nifi-registry-system-administrators-guide,System
Administrator’s Guide>>.
When an administrator navigates to the UI for the first time, the registry is
empty as there are no flow resources available to share yet:
diff --git a/nifi-stateless/nifi-stateless-assembly/README.md
b/nifi-stateless/nifi-stateless-assembly/README.md
index c853f463891..2beb5eb1c21 100644
--- a/nifi-stateless/nifi-stateless-assembly/README.md
+++ b/nifi-stateless/nifi-stateless-assembly/README.md
@@ -116,7 +116,7 @@ available, the dataflow will continue to trigger
MergeContent to run, without ma
(if configured) or the dataflow times out.
Additionally, depending on the context in which Stateless is run, triggering
the source components may not provide additional data.
-For example, if Stateless is run in an enviornment where data is queued up in
an Input Port and then the dataflow is triggered, subsequently
+For example, if Stateless is run in an environment where data is queued up in
an Input Port and then the dataflow is triggered, subsequently
triggering the Input Port to run will not produce additional data.
As a result, it is important to ensure that any dataflows that contain logic
to merge FlowFiles is configured with a Max Bin Age for MergeContent
@@ -210,7 +210,7 @@ The following properties may be used for configuring
security parameters:
| nifi.stateless.security.keystoreType | The type of the Keystore such as
PKCS12 | JKS |
| nifi.stateless.security.keystorePasswd | The password of the Keystore |
do-not-use-this-password-either |
| nifi.stateless.security.keyPasswd | An optional password for the key in the
Keystore. If not specified, the password of the Keystore itself will be used. |
password |
-| nifi.stateless.sensitive.props.key | The dataflow does not hold sensitive
passwords, but some processors may have a need to encrypt data before storing
it. This key is used to allow processors to encrypt and decrypt data. At
present, the only Processor supported by the community that makes use of this
feature is hte GetJMSTopic processor, which is deprecated. However, it is
provided here for completeness. | Some Passphrase That's Difficult to Guess |
+| nifi.stateless.sensitive.props.key | The dataflow does not hold sensitive
passwords, but some processors may have a need to encrypt data before storing
it. This key is used to allow processors to encrypt and decrypt data. At
present, the only Processor supported by the community that makes use of this
feature is the GetJMSTopic processor, which is deprecated. However, it is
provided here for completeness. | Some Passphrase That's Difficult to Guess |
| nifi.stateless.kerberos.krb5.file | The KRB5 file to use for interacting
with Kerberos. This is only necessary if the dataflow interacts with a
Kerberized data source/sink. If not specified, will default to `/etc/krb5.conf`
| /etc/krb5.conf |
A key tenant of NiFi is a separation between the framework and the extensions
that operate on data. As such, we must have a mechanism for dictating where
extensions can be located.
@@ -290,7 +290,7 @@ by specifying a local filename for the flow; by specifying
a URL for the flow; o
Note that if using a local filename, the format of the file is not the same as
the `flow.json.gz` file that NiFi uses but rather is the `Versioned Flow
Snapshot` format that is used by the NiFi Registry.
The easiest way to export a flow from NiFi onto local disk for use by
Stateless NiFi is to right-click on a Process Group or
-the canvas in NiFi and choose `Downlaod Flow`.
+the canvas in NiFi and choose `Download Flow`.
The following properties are supported for specifying the location of a flow:
@@ -314,7 +314,7 @@ Stateless NiFi also allows the user to provide one or more
Parameter Contexts to
For example, to create a Parameter Context with the name "Kafka Parameter
Context" and 2 parameters, "Kafka Topic" and "Kafka Brokers",
we would use the following three properties:
```
-nifi.stateless.parameters.kafka=Kafa Parameter Context
+nifi.stateless.parameters.kafka=Kafka Parameter Context
nifi.stateless.parameters.kafka.Kafka Topic=Sensor Data
nifi.stateless.parameters.kafka.Kafka
Brokers=kafka-01:9092,kafka-02:9092,kafka-03:9092
```
@@ -385,7 +385,7 @@ There is one additional property that is supported in the
dataflow configuration
|---------------|-------------|---------------|
| nifi.stateless.failure.port.names | A comma-delimited list of Output Port
names. If a FlowFile is routed to any of these Output Ports, it is considered a
failure and will rollback the entire session. | Unknown Kafka Type, Parse
Failure, Failed to Write to HDFS |
-This property allows the user to enter one or more ports that should be
considered failures. The value is a comma-separted list of names of Outport
Ports. In the example above, if a FlowFile is
+This property allows the user to enter one or more ports that should be
considered failures. The value is a comma-separated list of names of Output
Ports. In the example above, if a FlowFile is
routed to the "Unknown Kafka Type" port, the "Parse Failure" port, or the
"Failed to Write to HDFS" port, then the flow is considered a failure. The
entire session will be rolled back, and the source
Processor will not acknowledge the data from the source. As a result, the next
time that the dataflow is triggered, it will consume the same data again.
