Skip to content

Commit a242fc2

Browse files
Srivat97vaughnbetz
authored andcommitted
Header line: Fixing up spelling mistakes within the VTR documentation
THe words 'Navigate' and 'messages' were spelled incorrectly and they were found within the 'Commit Procedures' and 'Commit Messages and Structure' sections of the documentation. The words were replaced with the correct spelling.
1 parent ea49c34 commit a242fc2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.developers.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ The overall approach is similar, but we call out the differences below.
7272
7373
8. Create a Pull Request (PR) to request your changes be merged into VTR.
7474
75-
* Navitage to your branch on GitHub
75+
* Navigate to your branch on GitHub
7676
7777
a. **External Developers**
7878
@@ -92,7 +92,7 @@ The overall approach is similar, but we call out the differences below.
9292
9393
## Commit Messages
9494
95-
Commit messagaes are an important part of understanding the code base and it's history.
95+
Commit messages are an important part of understanding the code base and it's history.
9696
It is therefore *extremely* important to provide the following information in the commit message:
9797
9898
* What is being changed?

0 commit comments

Comments
 (0)