Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix typos in documentation files #311

Merged
merged 3 commits into from
Nov 11, 2024
Merged

fix typos in documentation files #311

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
dd80719
Update index.md
futreall Nov 9, 2024
5b1ae09
Update raising-an-issue.md
futreall Nov 9, 2024
7ad6c8f
Update index.md
futreall Nov 11, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion guidelines/raising-an-issue.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,6 @@ Issues specific to a project should first be raised within the project itself. E

There are several ways you can bring up an issue to the TOC. The most direct one is to simply open an issue in [the TOC GitHub repository](https://github.com/hyperledger/toc/issues) or to send an email to [the TOC mailing list](https://lists.hyperledger.org/g/toc/). Projects also submit [quarterly reports PRs](https://github.com/hyperledger/toc/pulls?q=is%3Aopen+is%3Apr+label%3Aquarterly-report) against which you can file a comment. Either way should get attention from the TOC.

Please, provide all relevant background information when raising an issue so that the TOC is fully equiped to process it. Failing to do so will lead the TOC to ask for that information as a first step and delay processing.
Please, provide all relevant background information when raising an issue so that the TOC is fully equipped to process it. Failing to do so will lead the TOC to ask for that information as a first step and delay processing.

If you are unsure about how to proceed or would like to raise an issue privately consider contacting one of the [Hyperledger Community Architects](https://wiki.hyperledger.org/display/CA/Community+Architects+Team) or one of the [TOC members](../members-info/toc-members.md). Community Architects can easily be contacted via email [community-architects@hyperledger.org](mailto:community-architects@hyperledger.org) or chat [#community-architects](https://discord.com/servers/hyperledger-foundation-905194001349627914).
4 changes: 2 additions & 2 deletions project-reports/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,8 +20,8 @@ Project updates are:

# Instructions for Filing
1. Copy the `0000-quarterly-update-template.md` file to the subdirectory for the current year and name the file `YYYY-Qn-Project-Name` (e.g., `2023-Q1-Hyperledger-Iroha.md`).
1. Update the information at the top of the file:
2. Update the information at the top of the file:
- change the `parent` line to `YYYY` (e.g., `parent: 2023`)
- change the `grand_parent` to `Project Updates` (i.e., `grand_parent: Project Updates`)
- remove the `nav_exclude` line
1. Text between `<mark></mark>` are instructions. Please remove when section has been completed.
3. Text between `<mark></mark>` are instructions. Please remove when section has been completed.