luke
/
iverilog
mirror of https://github.com/steveicarus/iverilog.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

typo fixes

This commit is contained in:
henry 2024-10-07 23:20:12 -05:00
parent 25a84d5cfc
commit 01d28ea277
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Documentation/developer/getting_started.rst
View File

@ -1,5 +1,5 @@
Getting Started as a Contributer
Getting Started as a Contributor
================================
Icarus Verilog development is centered around the github repository at
@ -218,7 +218,7 @@ first push the branch up to github:
Then go to github.com to create your pull request. `Create your pull request
against the "master" branch of the upstream repository
<https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork>`_,
or the version branch that you are working on. Your pull reuqest will be run
or the version branch that you are working on. Your pull request will be run
through continuous integration, and reviewed by one of the main
authors. Feedback may be offered to your PR, and once accepted, an approved
individual will merge it for you. Then you are done.

2
Documentation/developer/version_stamps.rst
View File

@ -9,7 +9,7 @@ These are the only files that have version information in them:
* verilog.spec -- Used to stamp RPM packages
When versions are changed, the above files need to be edited to account for
the new version information. The following used to have verion information in
the new version information. The following used to have version information in
them, but now their version information is generated:
The version_tag.h file is generated from git tag information using