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

Fix Grammar and Typo #2483

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Fix Grammar and Typo #2483

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
409efde
Update CONTRIBUTING.md
savvar9991 Dec 24, 2024
4f20c8d
Update SECURITY.md
savvar9991 Dec 24, 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 CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ The linter has been configured to ignore any folders called sample-app !!

### Linting pre-commit Workflow

The repository has been setup with a pre-commit hook that will lint any files that have been staged. This will prevent pushing any unlinted files to GitHub.
The repository has been set up with a pre-commit hook that will lint any files that have been staged. This will prevent pushing any unlinted files to GitHub.

You will need to fix any linting issues locally before being allowed to commit anything. You can either fix the linting issues manually or use the lint:path command with the --fix argument and specify the path to the files you want to lint fix.

Expand Down
2 changes: 1 addition & 1 deletion SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,4 +26,4 @@ Note as well that the Solidity language itself only guarantees security updates

## Legal

Smart contracts are a nascent techology and carry a high level of technical risk and uncertainty. Immutable's zkEVM Contracts are made available under the Apache-2.0 License, which disclaims all warranties in relation to the project and which limits the liability of those that contribute and maintain the project, including Immutable. In your use of this project, you are solely responsible for any use of Immutable zkEVM Contracts and you assume all risks associated with any such use. This Security Policy in no way evidences or represents an on-going duty by any contributor, including Immutable, to correct any flaws or alert you to all or any of the potential risks of utilizing the project.
Smart contracts are a nascent technology and carry a high level of technical risk and uncertainty. Immutable's zkEVM Contracts are made available under the Apache-2.0 License, which disclaims all warranties in relation to the project and which limits the liability of those that contribute and maintain the project, including Immutable. In your use of this project, you are solely responsible for any use of Immutable zkEVM Contracts and you assume all risks associated with any such use. This Security Policy in no way evidences or represents an on-going duty by any contributor, including Immutable, to correct any flaws or alert you to all or any of the potential risks of utilizing the project.