From 94cce889e8f68163db35139464abaae7c8085fe8 Mon Sep 17 00:00:00 2001
From: Danyll <37103154+Danyylka@users.noreply.github.com>
Date: Wed, 27 Nov 2024 16:28:04 +0100
Subject: [PATCH 1/3] fix typos README.md

---
 certora/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/certora/README.md b/certora/README.md
index cd85ba3d4c4..41ee720bd70 100644
--- a/certora/README.md
+++ b/certora/README.md
@@ -2,14 +2,14 @@
 
 These instructions detail the process for running Certora Verification Tool on OpenZeppelin Contracts.
 
-Documentation for CVT and the specification language are available [here](https://certora.atlassian.net/wiki/spaces/CPD/overview).
+Documentation for CVT and the specification language is available [here](https://certora.atlassian.net/wiki/spaces/CPD/overview).
 
 ## Prerequisites
 
 Follow the [Certora installation guide](https://docs.certora.com/en/latest/docs/user-guide/getting-started/install.html) in order to get the Certora Prover Package and the `solc` executable folder in your path.
 
 > **Note**
-> An API Key is required for local testing. Although the prover will run on a Github Actions' CI environment on selected Pull Requests.
+> An API Key is required for local testing. Although the prover will run on a GitHub Actions CI environment on selected Pull Requests.
 
 ## Running the verification
 

From c447dcfb9d9800713370eecfda84a7b80b7f2419 Mon Sep 17 00:00:00 2001
From: Danyll <37103154+Danyylka@users.noreply.github.com>
Date: Wed, 27 Nov 2024 16:30:35 +0100
Subject: [PATCH 2/3] Update 2017-03.md

---
 audits/2017-03.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/audits/2017-03.md b/audits/2017-03.md
index 4cd6dbfd30d..8ad620291d8 100644
--- a/audits/2017-03.md
+++ b/audits/2017-03.md
@@ -20,7 +20,7 @@ The git commit hash we evaluated is:
 
 # Disclaimer
 
-The audit makes no statements or warrantees about utility of the code, safety of the code, suitability of the business model, regulatory regime for the business model, or any other statements about fitness of the contracts to purpose, or their bugfree status. The audit documentation is for discussion purposes only.
+The audit makes no statements or warrantees about utility of the code, safety of the code, suitability of the business model, regulatory regime for the business model, or any other statements about fitness of the contracts to purpose, or their bug-free status. The audit documentation is for discussion purposes only.
 
 # Executive Summary
 

From b0561ee23472944133358344371a81c8b697184d Mon Sep 17 00:00:00 2001
From: Danyll <37103154+Danyylka@users.noreply.github.com>
Date: Wed, 27 Nov 2024 16:32:07 +0100
Subject: [PATCH 3/3] Update TESTING.md
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

“Unit tests are critical” should be “Unit tests are critical.” Plural "tests" are required to construct sentences.
---
 test/TESTING.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/test/TESTING.md b/test/TESTING.md
index a5ee9323ff4..321c7e592d6 100644
--- a/test/TESTING.md
+++ b/test/TESTING.md
@@ -1,3 +1,3 @@
 ## Testing
 
-Unit test are critical to OpenZeppelin Contracts. They help ensure code quality and mitigate against security vulnerabilities. The directory structure within the `/test` directory corresponds to the `/contracts` directory.
+Unit tests are critical to OpenZeppelin Contracts. They help ensure code quality and mitigate against security vulnerabilities. The directory structure within the `/test` directory corresponds to the `/contracts` directory.