From 72ce8cc18dc8045b6fa7abd2277cc26010492a30 Mon Sep 17 00:00:00 2001 From: Gaurav12480 Date: Tue, 28 Oct 2025 11:46:13 +0530 Subject: [PATCH 1/2] fix typo in documentation --- CONTRIBUTING.md | 2 +- README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index dd1de5b8..786cec11 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -19,7 +19,7 @@ Explain examples with code for these updates. 4. 🚨Always make a pull request against the `develop` branch. 5. Always have descriptive commit messages explaining what you did. 6. Always have a description for your pull request to explain what you did in-depth, it will be great if you include video recordings or screenshots if possible. -7. If you need help with the above please feel to reach out to me and I will help you out. +7. If you need help with the above please feel freeto reach out to me and I will help you out. ## Code reviews All submissions, including submissions by project members, require review. We use GitHub pull requests for this purpose. Consult [GitHub Help](https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) for more information on using pull requests. diff --git a/README.md b/README.md index 3851dd0e..c46b7a4a 100644 --- a/README.md +++ b/README.md @@ -60,7 +60,7 @@ _Notify_ focuses on the following key things: - Offline Capability - Notes. ✈️ - Clean and Simple Material UI. 🎨 - Dark mode. πŸŒ— -- Back/Restore feature. πŸ‘€ +- Backup/Restore feature. πŸ‘€ - Jetpack Compose UI. πŸ–Œ - Switch between layouts. 🌟 - Share the notes in the form of Text, Image & PDF πŸ“€ From 4a5fde69dc8275a1767ecd335eeb1f646247cb03 Mon Sep 17 00:00:00 2001 From: Gaurav Kumar Date: Tue, 28 Oct 2025 11:52:28 +0530 Subject: [PATCH 2/2] Fix typo in CONTRIBUTING.md --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 786cec11..691b4ef0 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -19,7 +19,7 @@ Explain examples with code for these updates. 4. 🚨Always make a pull request against the `develop` branch. 5. Always have descriptive commit messages explaining what you did. 6. Always have a description for your pull request to explain what you did in-depth, it will be great if you include video recordings or screenshots if possible. -7. If you need help with the above please feel freeto reach out to me and I will help you out. +7. If you need help with the above please feel free to reach out to me and I will help you out. ## Code reviews All submissions, including submissions by project members, require review. We use GitHub pull requests for this purpose. Consult [GitHub Help](https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) for more information on using pull requests.