Ajay Yadava created YETUS-456:
---------------------------------
Summary: Typos in documentation
Key: YETUS-456
URL: https://issues.apache.org/jira/browse/YETUS-456
Project: Yetus
Issue Type: Bug
Components: website and documentation
Reporter: Ajay Yadava
Assignee: Ajay Yadava
Priority: Trivial
While going through the documentation for test-patch I found some typos in the
documentation e.g.
asf-site-src/source/documentation/in-progress/precommit-advanced.md
{code}
-test-patch allows one to add to its basic feature set via plug-ins. There is
a directory called test-patch.d off of the directory where test-patch.sh lives.
Inside this directory one may place some bash shell fragments that, if
+test-patch allows one to add to its basic feature set via plug-ins. There is
a directory called test-patch.d inside the directory where test-patch.sh lives.
Inside this directory one may place some bash shell fragments that, if
{code}
{code}
- executed while determine which files trigger which tests. This function
+ executed while determining which files trigger which tests. This function
{code}
{code}
-funciton personality_globals
+function personality_globals
{code}
asf-site-src/source/documentation/in-progress/precommit-basic.md
{code}
-Luckily, test-patch supports provide ways to provide unified diffs via URLs.
+Luckily, test-patch supports ways to provide unified diffs via URLs.
{code}
/asf-site-src/source/documentation/in-progress/precommit-smart-apply-patch.md
{code}
-Its simpliest form is used when a patch is stored in a local file:
+Its simplest form is used when a patch is stored in a local file:
{code}
/precommit/smart-apply-patch.sh
{code}
- echo "test-patch.sh [OPTIONS] patch"
+ echo "smart-apply-patch.sh [OPTIONS] patch"
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
