Update Code of Conduct, Contributing Guidelines and Security.md

CODE_OF_CONDUCT.md

@@ -2,7 +2,7 @@
 
 ## Our Pledge
 
-We as members, contributors, and leaders pledge to make participation in our
+We as members, contributors, and leaders pledge to participate in our
 community a harassment-free experience for everyone, regardless of age, body
 size, visible or invisible disability, ethnicity, sex characteristics, gender
 identity and expression, level of experience, education, socio-economic status,
@@ -15,7 +15,7 @@ diverse, inclusive, and healthy community.
 ## Our Standards
 
 Examples of behavior that contributes to a positive environment for our
-community include:
+community includes:
 
 * Demonstrating empathy and kindness toward other people
 * Being respectful of differing opinions, viewpoints, and experiences
@@ -33,7 +33,7 @@ Examples of unacceptable behavior include:
 * Public or private harassment
 * Publishing others' private information, such as a physical or email
   address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
+* Other conduct that could reasonably be considered inappropriate in a
   professional setting
 
 ## Enforcement Responsibilities
@@ -50,7 +50,7 @@ decisions when appropriate.
 
 ## Scope
 
-This Code of Conduct applies within all community spaces, and also applies when
+This Code of Conduct applies within all community spaces and also applies when
 an individual is officially representing the community in public spaces.
 Examples of representing our community include using an official e-mail address,
 posting via an official social media account, or acting as an appointed
@@ -87,7 +87,7 @@ of actions.
 
 **Consequence**: A warning with consequences for continued behavior. No
 interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
+those enforcing the Code of Conduct, for a specified period. This
 includes avoiding interactions in community spaces as well as external channels
 like social media. Violating these terms may lead to a temporary or
 permanent ban.
@@ -98,7 +98,7 @@ permanent ban.
 sustained inappropriate behavior.
 
 **Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
+communication with the community for a specified period. No public or
 private interaction with the people involved, including unsolicited interaction
 with those enforcing the Code of Conduct, is allowed during this period.
 Violating these terms may lead to a permanent ban.

CONTRIBUTING.md

@@ -3,15 +3,15 @@ This repository **respects** people, despite their race, gender, religion, heigh
 
 -------------------------------------------------------------
 
-### DO NOT publish garbage PRs to farm Crypto AirDrops. Any user suspected of this actions will get banned. Submitting broken code wastes the time of the contributors, who have to spend their free time reviewing, fixing and testing code that does not even compile, does break other functionality or does not introduce any changes at all.  
+### DO NOT publish garbage PRs to farm Crypto AirDrops. Any user suspected of this action will get banned. Submitting broken code wastes the time of the contributors, who have to spend their free time reviewing, fixing, and testing code that does not even compile, does not break other functionality, or does not introduce any changes at all.  
 
 ---------------------------------
 
 
 
 # Contributing guidelines:
 
-Before reading: All of the rules below are guidelines, what means that they should be followed when possible. Please do not take them literally.
+Before reading: All of the rules below are guidelines, which means that they should be followed when possible. Please do not take them literally.
 
 ## Discussions:
  - This is the place to post any questions/doubts regarding WingetUI. Issues and feature requests should be posted in the [issues section](https://github.com/marticliment/WingetUI/issues).
@@ -21,21 +21,21 @@ Before reading: All of the rules below are guidelines, what means that they shou
 #### Issues:
  - Please use the BUG/ISSUE template
  - Please be clear when describing issues.
- - Please DO fill the form and DO NOT send empty issues with the information on the title.
+ - Please fill out the form and DO NOT send empty issues with the information on the title.
  - Please make sure to check for duplicates as said in the BUG/ISSUE template.
  - Please make sure to preceed titles with the `[BUG/ISSUE]` string, so they can be easily identified.
 
 #### Feature requests:
 - Please use the FEATURE REQUEST template
  - Please detail how the feature should work. Please be as specific as possible.
- - Some features are difficult, and might take some time to get implemented. This project is made on the contribur's free time, so please do not post messages asking for ETAs or similar. Every feature request will be considered.
+ - Some features are difficult and might take some time to get implemented. This project is made in the contributor's free time, so please do not post messages asking for ETAs or similar. Every feature request will be considered.
  - Please make sure to check for duplicates as said in the FEATURE REQUEST template.
  - Please make sure to preceed titles with the `[FEATURE REQUEST]` string, so they can be easily identified.
 
 ## Pull requests:
- - Please sppecify, either in the title or in the PR body text, the changes done. 
- - _Improvements_ pull request should have a list of the changes done in the body message, despite they being listed in the commits or not.
- - Draft pull requests should be properly identified as [draft pull requests](https://github.blog/2019-02-14-introducing-draft-pull-requests/) to avoid confusions.
+ - Please specify, either in the title or in the PR body text, the changes done. 
+ - _Improvements_ pull request should have a list of the changes done in the body message, whether they are listed in the commits or not.
+ - Draft pull requests should be properly identified as [draft pull requests](https://github.blog/2019-02-14-introducing-draft-pull-requests/) to avoid confusion.
  - When modifying/coding, please follow the guidelines below:
 
 ## Coding:
@@ -45,10 +45,10 @@ Before reading: All of the rules below are guidelines, what means that they shou
  - Constants should be written in capital letters, using underscores for spaces:
    - Example: `SYSTEM_DEFAULT_LOCALE = "ca-ES"`
  - Please specify, when possible, variable data types and function return types. More info [here](https://python.plainenglish.io/specifying-data-types-in-python-c182fda3bf43)
- - Try to add spaces and empty newlines to make code more human readable.
+ - Try to add spaces and empty newlines to make code more human-readable.
 
 ## Commits:
- - Commits must include only changes on one feature or section of the code. Let's say, you have fixed an issue regarding localisation and added a new entry in the settings section to change update frequency, those two changes must be committed separately.
+ - Commits must include only changes on one feature or section of the code. Let's say, you have fixed an issue regarding localization and added a new entry in the settings section to change update frequency, those two changes must be committed separately.
  - The code in each commit should be executable. Please do not leave work unfinished across commits, or, if it is needed, let the code be executed without errors.
- - Commit names must be clear and self-explanatory, and, if applicable, must reference the corresponding issue.
+ - Commit names must be self-explanatory, and, if applicable, must reference the corresponding issue.