Merge pull request #7596 from SITADRITA1/main

Grammar and Syntax Improvements in p5.js Documentation

Author: limzykenneth

.github/first-timers.yml

@@ -1,4 +1,4 @@
-# You can create the issue in a different repo than where the problem is. Just make sure you installed the bot on the configured repository.
+# You can create the issue in a different repo than where the problem is. Just make sure you have installed the bot on the configured repository.
 # The issue will link back to the original repository where the contribution will be made.
 repository: p5.js
 
@@ -11,4 +11,4 @@ labels:
   - hacktoberfest
 
 # If you would like to add your own template for the issue, add an .md file to your .github folder
-# template: .github/first-timers-issue-template.md 
+# template: .github/first-timers-issue-template.md 

contributor_docs/archive/es6-adoption.md

@@ -1,7 +1,7 @@
 ## ES6 Adoption
 p5.js has recently adopted the ECMAScript 2015 (ES6) language specifications in order to reduce the complexity of the codebase, increase readability, and utilize features that facilitate elegant and effective coding practices for both newcomers and seasoned contributors. 
 
-The transition process was initially [discussed](https://github.com/processing/p5.js/issues/3758) with the aim of migrating p5 to ES6, which later lead to a series of widespread syntactical changes in the codebase aligned with ES6 specifications. More info on the initial transition can be found [here](https://github.com/processing/p5.js/pull/3874). These changes consisted of minor modifications to the build system to facilitate processing, linting and testing the library based on ES6 standards, as well as major and ubiquitous syntactical modification in line with ES6 features.
+The transition process was initially [discussed](https://github.com/processing/p5.js/issues/3758) with the aim of migrating p5 to ES6, which later led to a series of widespread syntactical changes in the codebase aligned with ES6 specifications. More info on the initial transition can be found [here](https://github.com/processing/p5.js/pull/3874). These changes consisted of minor modifications to the build system to facilitate processing, linting and testing the library based on ES6 standards, as well as major and ubiquitous syntactical modification in line with ES6 features.
 
 It is worthy to note that as of writing this, these transformations are by no means complete, and do not reflect nor implement every possible feature of ES6. They are intended to facilitate a smoother transition to properly and efficiently utilize ES6 features if and when aligned with the community interests and standards. And serve to motivate contributors to gradually conform to the new style and features.
 

src/core/README.md

@@ -55,7 +55,7 @@ The `rendering.js` module presents the user-facing API for p5's various graphica
 
 ## [p5.Renderer.js](./p5.Renderer.js)
 
-The `p5.Renderer.js` module provides a common base definition for a p5 project output mode that can then be extended as with [p5.Renderer2D](./p5.Renderer2D.js). For three dimensional output, see the [webgl module](../webgl/). Each `p5` object instance typically has a `Renderer` attached as a property.
+The `p5.Renderer.js` module provides a common base definition for a p5 project output mode that can then be extended as with [p5.Renderer2D](./p5.Renderer2D.js). For three-dimensional output, see the [webgl module](../webgl/). Each `p5` object instance typically has a `Renderer` attached as a property.
 
 ## [p5.Renderer2D.js](./p5.Renderer2D.js)