Update Contributing and Standard files

.github/CONTRIBUTING.md → CONTRIBUTING.md

@@ -6,13 +6,13 @@ Start at [GitHub - WordPress/Community-Team](https://github.com/WordPress/Commun
 
 Install the bookmarklet here:
 
-https://wordpress.github.io/Community-Team/
+<https://wordpress.github.io/Community-Team/>
 
 **Installation:**
- 
+
 > Drag the issue creator button to your bookmarks bar to install.
 
-**Usage**
+### Usage
 
 1. Open the event tracker to a specific event needing vetting.
 2. Click on the issue creator button link in your bookmarks bar and confirm.
@@ -22,82 +22,63 @@ https://wordpress.github.io/Community-Team/
 
 ## Create new Event Tracking issue
 
-### Requirements:
+### Requirements
 
-* Access to [GitHub - WordPress/Community-Team](https://github.com/WordPress/Community-Team)  repository on Github
+* Access to [GitHub - WordPress/Community-Team](https://github.com/WordPress/Community-Team) repository on Github
 * Access to WordCamp and Meetup Tracker
-* Helpscout - [support@wordcamp.org](mailto:support@wordcamp.org) \
+* Helpscout - [support@wordcamp.org](mailto:support@wordcamp.org)
 
 If you do not have access to any one of these, you will not be able to vet applications. Please ask someone for access [#community-team](https://wordpress.slack.com/archives/C037W5S7X)
 
 ### Creating an issue
 
 * Log into GitHub
-* Open the [GitHub - WordPress/Community-Team](https://github.com/WordPress/Community-Team) 
+* Open the [GitHub - WordPress/Community-Team](https://github.com/WordPress/Community-Team)
 * Open the [Issues](https://github.com/WordPress/Community-Team/issues) tab
 
-
 #### Click on the New Issue button
 
 ![step-1](https://github.com/WordPress/Community-Team/assets/4948323/6761a686-039a-4f33-9a09-594338a38a0f)
 
--
-
 ![step-2](https://github.com/WordPress/Community-Team/assets/4948323/bc7ed9d2-2d39-4faf-a68a-dfce884306d3)
 
-#### Select Event Application Vetting - ‘Get started’
+#### Select Event Application Vetting - 'Get started'
 
 ![step-3](https://github.com/WordPress/Community-Team/assets/4948323/c03e468a-b5e4-48a6-94c4-4884d6f2eb23)
 
-
 #### Click on the button Submit new issue
-- In the Title field, add: event type (Meetup, for example), city/event name, and link to the tracker
-- Add the labels for event type (meetups or WordCamp)
 
+* In the Title field, add: event type (Meetup, for example), city/event name, and link to the tracker
+* Add the labels for event type (meetups or WordCamp)
 
 ![step-4](https://github.com/WordPress/Community-Team/assets/4948323/c63b2b89-2959-4d21-9d21-db9013f9bba2)
 
+#### Click on the button Todo / Ready
 
-#### Click on the button  Todo / Ready
-
-- There is no need at this stage to assign the issue to someone, team leads will do it later
-- Neither is it necessary to select the project, it will be automatically assigned to the 
-Community Team 2024 Project Board 
-- If everything looks good, scroll the page and click on "Submit New Issue".
-
+* There is no need at this stage to assign the issue to someone, team leads will do it later
+* Neither is it necessary to select the project, it will be automatically assigned to the Community Team 2024 Project Board
+* If everything looks good, scroll the page and click on "Submit New Issue".
 
 ![step-5](https://github.com/WordPress/Community-Team/assets/4948323/dadc5b6b-2e41-4341-9947-a00f2f1e906c)
 
-
 #### Issue assignment
 
 Once the issue is created, you can assign it to yourself or to a teammate
 
-
 ![step-6](https://github.com/WordPress/Community-Team/assets/4948323/9968f56c-ef2a-4553-b93c-780a64ab5f3f)
 
 > You can comment `/claim` to self-assign an issue.
 
-<img width="1058" alt="claim" src="https://github.com/WordPress/Community-Team/assets/4948323/1f6d5f97-4344-4d79-9d2e-1edbfb9c22db">
-
 > You can also assign to teammates in the dropdown
 
-<img width="364" alt="assign" src="https://github.com/WordPress/Community-Team/assets/4948323/20fc06fb-12e4-47d2-a9ac-f215927d38f5">
-
-
 > Make sure to set the status as Todo/Ready
 
-
-<img width="531" alt="status" src="https://github.com/WordPress/Community-Team/assets/4948323/ad655ced-8b0d-4b29-b587-8d835c1fd566">
-
-
 #### Application Review Process on GitHub
 
-> Once you’ve received the issue assigned to yourself, you’ll use GitHub just to track the progress, but the whole process will be carried out using the event tracker and HelpScout [as usual](https://make.wordpress.org/community/handbook/community-deputy/resources-and-tools/application-review/). - - - Please never share your vetting notes on GitHub, only in the event tracker as we always do.
+> Once you’ve received the issue assigned to yourself, you’ll use GitHub just to track the progress, but the whole process will be carried out using the event tracker and HelpScout [as usual](https://make.wordpress.org/community/handbook/community-deputy/resources-and-tools/application-review/). Please never share your vetting notes on GitHub, only in the event tracker as we always do.
 
 * Update the status to In Progress
 * If you need a second opinion or help from teammates, while you wait for their feedback please update the status to In Review
 * If you need, you can leave a comment on the issue:
 
-
-- Once you’ve completed the entire application review process: tracker updated and email sent to organizer for inviting to orientation or reject the application, please update the status to Complete, scroll the page until the bottom, and close the issue.
+Once you’ve completed the entire application review process: tracker updated and email sent to organizer for inviting to orientation or reject the application, please update the status to Complete, scroll the page until the bottom, and close the issue.