Move Fellowship Guides

docs/learn/learn-guides-polkadot-opengov.md

@@ -327,3 +327,56 @@ within the track, and a
 have been met. Failing to submit the decision deposit within a
 {{ polkadot: <RPC network="polkadot" path="consts.referenda.undecidingTimeout" defaultValue={201600} filter="blocksToDays"/> :polkadot }}{{ kusama: <RPC network="kusama" path="consts.referenda.undecidingTimeout" defaultValue={201600} filter="blocksToDays"/> :kusama }}-day
 period will lead to a referendum timeout.
+
+## Becoming a Member of the Technical Fellowship
+
+Before starting the candidate induction process, please ensure the candidate account is active and
+has a balance greater than the existential deposit of the collectives system chain (0.1 DOT). It is
+recommended that the candidate account also has a verified identity.
+
+The first step is to add a preimage on the collectives system chain. This preimage should include
+the call to `induct` a candidate account, as shown below. The preimage can be added by any account
+on the collectives system chain. The preimage hash of this call will later be used for creating a
+fellowship referenda with an approriate origin and track.
+
+![candidate-induct](../assets/fellowship-induct-candidate.png)
+
+The next step is to create a fellowship referenda, which can only be done by a pre-existing
+Technical Fellowship member. When a fellowship member navigates to Governance > Fellowship >
+Referenda, they should be able to see a submit proposal button. In the example below,submission
+track is chosen as `1/members`, origin as `FellowshipOrigins` and fellowship origins as `Members`.
+This selection should work for inducting an account without any rank to the fellowship as a
+candidate with rank 0. After copying the preimage hash in the designated field, the preimage length
+will automatically be populated.
+
+![candidate-induct-proposal](../assets/fellowship-candidate-proposal.png)
+
+After submitting the proposal, the voting can commence. A decision deposit needs to be placed for
+this fellowship referendum to be decided. After the fellowship referenda successfully passes, the
+candidate is successfully inducted into the Polkadot Fellowship with rank 0.
+
+### Rank Updates
+
+The Polkadot Technical Fellowship members are expected to provide a periodic evidence to request for
+retaining their rank or to get promoted to a higher rank. Any fellowship member upto rank 4 can be
+promoted to the next rank through a fellowship referenda that can be voted by the members who are 2
+ranks higher. For instance, the fellowship
+[referenda 64](https://collectives.subsquare.io/fellowship/referenda/64) which promotes a member
+from rank 1 to rank 2 can only be voted by members whose ranks are greater than or equal to 3.
+Promotion of the Polkadot Fellowship members from rank 5 needs to be done through an OpenGov
+referendum.
+
+This preimage example should include the call to `promote` an account to a specific rank, as shown
+below. This preimage can be added by any account on the collectives system chain.
+
+![candidate-promote](../assets/fellowship-promote-member.png)
+
+In the snapshot below, the submission track is chosen as `21/Promote to I Dan`, origin as
+`FellowshipOrigins` and fellowship origins as `PromoteTo1Dan`. This selection should work for
+promoting a candidate with rank 0 to a member with rank 1.
+
+![candidate-promote-proposal](../assets/fellowship-promotion-proposal.png)
+
+For promoting a member from Rank 1 to Rank 2, the submission track can be chosen as
+`22/Promote to  II Dan`, origin as `FellowshipOrigins` and fellowship origins as `PromoteTo2Dan`.
+Only the members with Rank >= 3 can vote on this proposal.

docs/learn/learn-polkadot-technical-fellowship.md

@@ -90,13 +90,12 @@ amounts for each ranked members.
 | VIII | Master Constant |   $200,000    |
 |  IX  |  Grand Master   |   $200,000    |
 
-## Membership Management
+## Becoming a Member
 
 The Polkadot technical Fellowship was initally [seeded](https://github.com/polkadot-fellows/seeding)
 with its members and their corresponding ranks, and got
 [added on to Polkadot's Collectives](https://polkadot.polkassembly.io/motion/403) system chain. All
-new membership requests will go through the fellowship governance and the procedure is outlined in
-the section below.
+new membership requests will go through the fellowship governance.
 
 ### Becoming a Member
 
@@ -129,56 +128,9 @@ pallet.
 
 :::
 
-Before starting the candidate induction process, please ensure the candidate account is active and
-has a balance greater than the existential deposit of the collectives system chain (0.1 DOT). It is
-recommended that the candidate account also has a verified identity.
-
-The first step is to add a preimage on the collectives system chain. This preimage should include
-the call to `induct` a candidate account, as shown below. The preimage can be added by any account
-on the collectives system chain. The preimage hash of this call will later be used for creating a
-fellowship referenda with an approriate origin and track.
-
-![candidate-induct](../assets/fellowship-induct-candidate.png)
-
-The next step is to create a fellowship referenda, which can only be done by a pre-existing
-Technical Fellowship member. When a fellowship member navigates to Governance > Fellowship >
-Referenda, they should be able to see a submit proposal button. In the example below,submission
-track is chosen as `1/members`, origin as `FellowshipOrigins` and fellowship origins as `Members`.
-This selection should work for inducting an account without any rank to the fellowship as a
-candidate with rank 0. After copying the preimage hash in the designated field, the preimage length
-will automatically be populated.
-
-![candidate-induct-proposal](../assets/fellowship-candidate-proposal.png)
-
-After submitting the proposal, the voting can commence. A decision deposit needs to be placed for
-this fellowship referendum to be decided. After the fellowship referenda successfully passes, the
-candidate is successfully inducted into the Polkadot Fellowship with rank 0.
-
-### Rank Updates
-
-The Polkadot Technical Fellowship members are expected to provide a periodic evidence to request for
-retaining their rank or to get promoted to a higher rank. Any fellowship member upto rank 4 can be
-promoted to the next rank through a fellowship referenda that can be voted by the members who are 2
-ranks higher. For instance, the fellowship
-[referenda 64](https://collectives.subsquare.io/fellowship/referenda/64) which promotes a member
-from rank 1 to rank 2 can only be voted by members whose ranks are greater than or equal to 3.
-Promotion of the Polkadot Fellowship members from rank 5 needs to be done through an OpenGov
-referendum.
-
-This preimage example should include the call to `promote` an account to a specific rank, as shown
-below. This preimage can be added by any account on the collectives system chain.
-
-![candidate-promote](../assets/fellowship-promote-member.png)
-
-In the snapshot below, the submission track is chosen as `21/Promote to I Dan`, origin as
-`FellowshipOrigins` and fellowship origins as `PromoteTo1Dan`. This selection should work for
-promoting a candidate with rank 0 to a member with rank 1.
-
-![candidate-promote-proposal](../assets/fellowship-promotion-proposal.png)
-
-For promoting a member from Rank 1 to Rank 2, the submission track can be chosen as
-`22/Promote to  II Dan`, origin as `FellowshipOrigins` and fellowship origins as `PromoteTo2Dan`.
-Only the members with Rank >= 3 can vote on this proposal.
+Follow
+[these Polkadot-JS guides](./learn-guides-polkadot-opengov.md#becoming-a-member-of-the-technical-fellowship)
+to learn how to become a member of the Polkadot Technical Fellowship.
 
 #### Retain Rank