Apply suggestions from code review

Wording and grammar changes for CONTRIBUTING and README

Author: tuturu-tech

CONTRIBUTING.md

@@ -29,10 +29,10 @@ Here's a basic overview of Building-Secure-Contracts' structure:
 
 ```text
 .
-├── development-guidelnes # High-level best practices for all smart contracts
+├── development-guidelines # High-level best practices for all smart contracts
 ├── learn_evm # EVM technical knowledge
 ├── not-so-smart-contracts # Examples of common smart contract issues, including descriptions, examples, and recommendations
-├── program-analysis # How to utilize automated tools for securing contracts
+├── program-analysis # How to utilize automated tools to secure contracts
 ├── resources # Various online resources
 └── ...
 ```

README.md

@@ -2,16 +2,16 @@
 
 ![](https://github.com/crytic/building-secure-contracts/workflows/CI/badge.svg) ![](https://github.com/crytic/building-secure-contracts/workflows/Echidna/badge.svg)
 
-Brought to you by [Trail of Bits](https://www.trailofbits.com/), this repository offers guidelines and best practices for developing secure smart contracts. Contributions are welcome, so please participate by adhering to our [contributing guidelines](https://github.com/crytic/building-secure-contracts/blob/master/CONTRIBUTING.md).
+Brought to you by [Trail of Bits](https://www.trailofbits.com/), this repository offers guidelines and best practices for developing secure smart contracts. Contributions are welcome, you can contribute by following our [contributing guidelines](https://github.com/crytic/building-secure-contracts/blob/master/CONTRIBUTING.md).
 
 **Table of Contents:**
 
 - [Development Guidelines](./development-guidelines)
-  - [High-Level Best Practices](./development-guidelines/guidelines.md): Essential practices for all smart contracts
-  - [Incident Response Recommendations](./development-guidelines/incident_response.md): Advice for creating an incident response plan
+  - [High-Level Best Practices](./development-guidelines/guidelines.md): Best practices for all smart contracts
+  - [Incident Response Recommendations](./development-guidelines/incident_response.md): Guidelines for creating an incident response plan
   - [Secure Development Workflow](./development-guidelines/workflow.md): A high-level process to follow during code development
   - [Token Integration Checklist](./development-guidelines/token_integration.md): What to check when interacting with arbitrary tokens
-- [Learn EVM](./learn_evm): Technical knowledge about EVM
+- [Learn EVM](./learn_evm): Technical knowledge about the EVM
   - [EVM Opcodes](./learn_evm/evm_opcodes.md): Information on all EVM opcodes
   - [Transaction Tracing](./learn_evm/tracing.md): Helper scripts and guidance for generating and navigating transaction traces
   - [Yellow Paper Guidance](./learn_evm/yellow-paper.md): Symbol reference for easier reading of the Ethereum yellow paper
@@ -28,13 +28,13 @@ Brought to you by [Trail of Bits](https://www.trailofbits.com/), this repository
 - [Program Analysis](./program-analysis): Using automated tools to secure contracts
   - [Echidna](./program-analysis/echidna): A fuzzer that checks your contract's properties
   - [Slither](./program-analysis/slither): A static analyzer with both CLI and scriptable interfaces
-  - [Manticore](./program-analysis/manticore): A symbolic execution engine that proves correctness properties
-  - Each tool comes with:
+  - [Manticore](./program-analysis/manticore): A symbolic execution engine that proves the correctness of properties
+  - For each tool, this training material provides:
     - A theoretical introduction, an API walkthrough, and a set of exercises
     - Exercises that take approximately two hours to gain practical understanding
 - [Resources](./resources): Assorted online resources
   - [Trail of Bits Blog Posts](./resources/tob_blogposts.md): A list of blockchain-related blog posts created by Trail of Bits
 
 # License
 
-Secure-contracts and building-secure-contracts are licensed and distributed under the [AGPLv3 license](https://github.com/crytic/building-secure-contracts/blob/master/LICENSE). Please contact us if you require an exception to the terms.
+secure-contracts and building-secure-contracts are licensed and distributed under the [AGPLv3 license](https://github.com/crytic/building-secure-contracts/blob/master/LICENSE). Contact us if you're looking for an exception to the terms.