NIFI-4091 - typo fixes
diff --git a/src/pages/markdown/licensing-guide.md b/src/pages/markdown/licensing-guide.md
index 8da9d33..2c6be1d 100644
--- a/src/pages/markdown/licensing-guide.md
+++ b/src/pages/markdown/licensing-guide.md
@@ -63,7 +63,7 @@
dependencies then you should create or edit the LICENSE and/or NOTICE local to that subcomponent AND modify the
NOTICE and/or LICENSE of the top level nifi source.
-In the case of subcomponents which produce binary artifacts which themselves can bunde 3rd party works (as would be
+In the case of subcomponents which produce binary artifacts which themselves can bundle 3rd party works (as would be
typical in a NAR, WAR, tar.gz, zip bundle) then you must ensure that the subcomponent binary artifact itself includes
a full and complete LICENSE and/or NOTICE as needed to cover those 3rd party works. For every modification to the
subcomponent LICENSE/NOTICE for a given 3rd party work the overall Apache NiFi source and binary LICENSE/NOTICE pairs
@@ -76,10 +76,10 @@
### How to go about working with the LICENSE/NOTICE modifications
-If the dependency is a source dependency (ie you copied in javascript, css, java source files from a website) then you
+If the dependency is a source dependency (for example: you copied in javascript, css, java source files from a website) then you
must ensure it is from [Category-A](https://www.apache.org/legal/resolved.html#category-a) licenses.
-If the dependency is a binary dependency (ie maven pulled in a jar file) then you must ensure it is either from
+If the dependency is a binary dependency (for example: maven pulled in a jar file) then you must ensure it is either from
[Category-A](https://www.apache.org/legal/resolved.html#category-a) or
[Category-B](https://www.apache.org/legal/resolved.html#category-b).
diff --git a/src/pages/markdown/minifi/system-admin-guide.md b/src/pages/markdown/minifi/system-admin-guide.md
index 2ab71c5..de19c01 100644
--- a/src/pages/markdown/minifi/system-admin-guide.md
+++ b/src/pages/markdown/minifi/system-admin-guide.md
@@ -219,7 +219,7 @@
inputPorts | A list of every input port for this RPG and their status. Their status includes it's name, whether the target exit and whether it's currently running.
stats | The current stats of the RPG. This includes the active threads, sent content size and count.
-An example query to get the health, bulletins, input ports and stats of all the RPGS is below.
+An example query to get the health, bulletins, input ports and stats of all the RPGs is below.
```
minifi.sh flowStatus remoteprocessgroup:all:health,bulletins,inputports,stats
diff --git a/src/pages/markdown/quickstart.md b/src/pages/markdown/quickstart.md
index 7be2b56..e6e67be 100644
--- a/src/pages/markdown/quickstart.md
+++ b/src/pages/markdown/quickstart.md
@@ -12,7 +12,7 @@
## Issue Tracking
-Track issues on the "NIFI" Project on the Apache Jira ([browse][jira]).
+Track issues on the "NIFI" Project on the Apache JIRA ([browse][jira]).
## Building
@@ -158,7 +158,7 @@
With the default settings you can point a web browser at `http://localhost:8080/nifi/`
-Logging is configured by default to log to `./logs/nifi-app.log`. The following log message should indicate the web ui
+Logging is configured by default to log to `./logs/nifi-app.log`. The following log message should indicate the web UI
is ready for use:
2014-12-09 00:42:03,540 INFO [main] org.apache.nifi.web.server.JettyServer NiFi has started. The UI is available at the following URLs:
diff --git a/src/pages/markdown/release-guide.md b/src/pages/markdown/release-guide.md
index 93c8419..0303ef3 100644
--- a/src/pages/markdown/release-guide.md
+++ b/src/pages/markdown/release-guide.md
@@ -62,7 +62,7 @@
"```/tmp/src/nifi-${NIFI_VERSION}```" is seen in an instruction or email template it should be replaced with
"```/tmp/src/nifi-0.7.0```" when working the release of "Apache NiFi 0.7.0".
- * Subtitutions used in tasks and email templates
+ * Substitutions used in tasks and email templates
<pre>
Reference Example value Description
========= ============== ===========
@@ -72,7 +72,7 @@
${JIRA_TICKET} NIFI-2112 the JIRA ticket created by the release manager for the release tasks.
${RC} 2 the Release Candidate index start at 1 for the first release candidate.
${RC_TAG_COMMIT_ID} the 40 byte commit ID of the RC tag created during the Maven release process.
- ${STAGING_REPO_ID} orgapachenifi-1088 the temporate repository ID where staged artifacts have been placed.
+ ${STAGING_REPO_ID} orgapachenifi-1088 the temporary repository ID where staged artifacts have been placed.
${RM_USERID} johndoe the Apache account ID of Release Manager.
${RELEASE_TAG} rel/nifi-0.7.0 the Git repository tag for the source code as released.
${VOTE_THREAD_URL} [0.7.0 vote thread][070-rc2-vote] the URL for the Apache Pony Mail archive of the release vote thread.
@@ -407,7 +407,7 @@
Thank you for your time and effort to validate the release!
```
-1. Developers in the community review the release candiate and reply to the vote email with their vote.
+1. Developers in the community review the release candidate and reply to the vote email with their vote.
1. After 72 hours if
- at least 3 binding (PMC members) cast +1 votes, and
- the positive binding votes out number any negative binding votes