diff --git a/docs/outreach/experience.md b/docs/outreach/experience.md
index 4f5ce2b20b..bafa093dac 100644
--- a/docs/outreach/experience.md
+++ b/docs/outreach/experience.md
@@ -201,6 +201,8 @@ In practice, this means that over the course of the program, you will:
   questions about what to tackle next in your
   [check-ins](#how-to-post-your-check-ins).
 
+- Use GitHub project boards to understand current priorities.
+
 - Like other Zulip contributors, [claim
   issues](../contributing/contributing.md#claiming-an-issue) only when you
   actually start work on them.
@@ -234,35 +236,16 @@ Always keep the following order of priorities in mind:
 
 6. Finally, if all of the above are in good shape, **find a new issue** to pick up!
 
-### What about my proposal?
 
-We have a fluid approach to planning, which means you are very unlikely to end
-up working on the exact set of issues described in your proposal. Your proposal
-is not a strict commitment (on either side).
+### Finding issues to pick up
 
-In terms of managing your work:
+You can use the following process to find a new issue to work on:
 
-- Regardless of whether an issue was mentioned in your proposal, make
-  sure you bring it up in your check-ins when you plan to start
-  working on something. Project priorities shift over time, and we
-  may have suggestions for higher-priority work in your area of
-  interest, or issues that will serve as good preparation for other
-  work you are excited about. It's also possible that a project idea
-  is not ready to be worked on, or needs to be sequenced after other projects.
+1. Check the issue tracker for bugs in the parts of the codebase you've been
+   working in. Bugs and polish
+  make a huge difference to our users' experience. If you can put up a clean PR 
 
-- When asking for recommendations for what to work on next, it's helpful to
-  include a reminder of what areas you're most excited about, especially early
-  on in the program when we're still getting to know you. Do not expect program
-  administrators to remember what issues were listed in your proposal.
-
-While some program participants stick closely to the spirit of their proposal,
-others find new areas they are excited about in the course of their work. You
-can be highly successful in the program either way!
-
-### Tips for finding issues to pick up
-
-- Look for, claim, and fix bugs to help keep Zulip polished. Bugs and polish
-  make a huge difference to our users' experience. If you can fix a
+- Look for, claim, and fix bugs to help keep Zulip polished. B If you can fix a
   [high-priority
   bug](https://github.com/zulip/zulip/issues?page=2&q=is%3Aopen+is%3Aissue+label%3Abug+label%3A%22priority%3A+high%22)
   in an area you've been working on, it is likely to have more impact than any
@@ -295,6 +278,32 @@ waiting for a question to be answered or for the next round of feedback on a PR:
   preparatory refactoring that will make the feature easier to complete and can
   already be merged.
 
+### What about my proposal?
+
+We have a fluid approach to planning, which means you are very unlikely to end
+up working on the exact set of issues described in your proposal. Your proposal
+is not a strict commitment (on either side).
+
+In terms of managing your work:
+
+- Regardless of whether an issue was mentioned in your proposal, make
+  sure you bring it up in your check-ins when you plan to start
+  working on something. Project priorities shift over time, and we
+  may have suggestions for higher-priority work in your area of
+  interest, or issues that will serve as good preparation for other
+  work you are excited about. It's also possible that a project idea
+  is not ready to be worked on, or needs to be sequenced after other projects.
+
+- When asking for recommendations for what to work on next, it's helpful to
+  include a reminder of what areas you're most excited about, especially early
+  on in the program when we're still getting to know you. Do not expect program
+  administrators to remember what issues were listed in your proposal.
+
+While some program participants stick closely to the spirit of their proposal,
+others find new areas they are excited about in the course of their work. You
+can be highly successful in the program either way!
+
+
 ## How else can I contribute?
 
 - Participate and be helpful in the community! Helping a new contributor get