diff options
| author | gritbub <38131016+gritbub@users.noreply.github.com> | 2018-06-02 16:50:42 -0500 |
|---|---|---|
| committer | gritbub <38131016+gritbub@users.noreply.github.com> | 2018-06-02 16:50:42 -0500 |
| commit | e2d965ab360ab077b408d4819dd0a2000ff132d8 (patch) | |
| tree | 1ad86adc0cb51e6d30f5b6e2b61c84f3efd9841c /doc | |
| parent | 8122c18944b69305060b03fad5b5a46ca59c0975 (diff) | |
| download | ghdl-e2d965ab360ab077b408d4819dd0a2000ff132d8.tar.gz ghdl-e2d965ab360ab077b408d4819dd0a2000ff132d8.tar.bz2 ghdl-e2d965ab360ab077b408d4819dd0a2000ff132d8.zip | |
Change pronouns from singular to plural.
Address 3 requested changes:
-[Meta](https://github.com/ghdl/ghdl/pull/591/files#r192524451)
-[Roadmap](https://github.com/ghdl/ghdl/pull/591/files#r192524641)
-[ImplementationOfVHDL](https://github.com/ghdl/ghdl/pull/591/files#r192529073)
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/appendix/Meta.rst | 2 | ||||
| -rw-r--r-- | doc/appendix/Roadmap.rst | 2 | ||||
| -rw-r--r-- | doc/references/ImplementationOfVHDL.rst | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/doc/appendix/Meta.rst b/doc/appendix/Meta.rst index ac1558c42..2430e6f45 100644 --- a/doc/appendix/Meta.rst +++ b/doc/appendix/Meta.rst @@ -63,7 +63,7 @@ General guidelines to edit the documentation Guidelines to edit section 'Building' ************************************* -I prefer a text block, which explains how a compilation works, what I can configure for that backend, etc. After that, I prefer a code block with e.g. bash instructions on how to compile a backend. A list of instructions with embedded bash lines is not helpful. An experienced, as well as novice user, would like to copy a set of instructions into the shell. But it should be stated what these instructions will do. Complex flows like for GCC, can be split into multiple shell code blocks. Moreover, I find it essential to demonstrate when and where to change directories. +We prefer a text block, which explains how a compilation works, what we can configure for that backend, etc. After that, we prefer a code block with e.g. bash instructions on how to compile a backend. A list of instructions with embedded bash lines is not helpful. An experienced, as well as novice user, would like to copy a set of instructions into the shell. But it should be stated what these instructions will do. Complex flows like for GCC, can be split into multiple shell code blocks. Moreover, we find it essential to demonstrate when and where to change directories. We would like to see a list like: diff --git a/doc/appendix/Roadmap.rst b/doc/appendix/Roadmap.rst index c0da61635..19f673e81 100644 --- a/doc/appendix/Roadmap.rst +++ b/doc/appendix/Roadmap.rst @@ -3,7 +3,7 @@ Roadmap | Future Improvements ############################# -I have several axes for `GHDL` improvements: +We have several axes for `GHDL` improvements: * Documentation * Better diagnostics messages (warning and error) diff --git a/doc/references/ImplementationOfVHDL.rst b/doc/references/ImplementationOfVHDL.rst index 4aa8b3a71..0074d2c7c 100644 --- a/doc/references/ImplementationOfVHDL.rst +++ b/doc/references/ImplementationOfVHDL.rst @@ -397,7 +397,7 @@ Using GRT from Ada .. warning:: This topic is only for advanced users who know how to use `Ada` - and `GNAT`. This is provided only for reference; I have tested + and `GNAT`. This is provided only for reference; we have tested this once before releasing `GHDL` 0.19, but this is not checked at each release. |