Updated CONTRIBUTING.md to account for new project planning board (#10104)

Update CONTRIBUTING.md

Author: yaira2

.github/CONTRIBUTING.md

@@ -10,11 +10,7 @@ all community interactions must abide by the [Code of Conduct](https://github.co
 
 ## Finding issues you can help with
 Looking for something to work on?
-Issues marked [``triage approved``](https://github.com/files-community/Files/issues?q=is%3Aopen+is%3Aissue+label%3A%22triage+approved%22)
-are a good place to start.
-
-You can also check the [``help wanted``](https://github.com/files-community/Files/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) tag to find 
-other issues to help with. If you're interested in working on a fix, leave a comment to let everyone know and to help
+Issues marked as ready to build are a good place to start. If you're interested in working on an issue, leave a comment to let everyone know and to help
 avoid duplicated effort from others.
 
 ## Contributions we accept
@@ -29,11 +25,9 @@ improvements which address the top issues reported by Files users. Some general
    pull request.
 * **DO** write a good description for your pull request. More detail is better. Describe *why* the change is being 
    made and *why* you have chosen a particular solution. Describe any manual testing you performed to validate your change.
-* **DO NOT** submit a PR unless it is linked to an Issue marked 
-   [`triage approved`](https://github.com/files-community/Files/issues?q=is%3Aopen+is%3Aissue+label%3A%22triage+approved%22). 
-   This enables us to have a discussion on the idea before anyone invests time in an implementation.
+* **DO NOT** submit a PR unless it the connected issue is marked as ready to build or approved indirectly by an org member. 
+   This enables us to have a discussion on the idea before anyone invests time on the implementation.
 * **DO NOT** merge multiple changes into one PR unless they have the same root cause.
-* **DO NOT** submit pure formatting/typo changes to code that has not been modified otherwise.
 
 > Submitting a pull request for an approved Issue is not a guarantee it will be approved.
 > The change must meet our high bar for code quality, architecture, and performance.
@@ -53,8 +47,7 @@ After installing WinAppDriver, you will need to run the Files.Package at least o
 Once you have the debug version registered, you can run the tests from the test explorer in Visual Studio.
 
 ## Review Process
-After submitting a pull request, members of the Files team will review your code. We will
-assign the request to an appropriate reviewer. Any member of the community may
+After submitting a pull request, members of the Files team will review your code. Any member of the community may
 participate in the review, but at least one member of the Files team will ultimately approve
 the request.