mostly to make a real link for the policy, wrap paragraphs so they are
more readable in plain text, and make a bullet list for the
revocation policy, and clarify each part is a "or"

howto/conference.md

@@ -334,25 +334,44 @@ N/A. Meet.coop has a [disclaimer][] that serves as a terms of service.
 <!-- community wiki, in: https://gitlab.torproject.org/tpo/community/team/-/wikis/Tor-Project-BBB-Account-Policy -->
 <!-- the above shouldn't be changed without also changing those -->
 
-1. Any Tor Core Contributor can request a BBB account, and it can stay active as long as they remain a core contributor. https://gitweb.torproject.org/community/policies.git/tree/membership.txt
+1. Any [Tor Core Contributor](https://gitweb.torproject.org/community/policies.git/tree/membership.txt) can request a BBB account, and it can
+   stay active as long as they remain a core contributor.
 
-2. Organizations and individuals, who are active partners of the Tor Project can request an account and use for their activities.
+2. Organizations and individuals, who are active partners of the Tor
+   Project can request an account and use for their activities.
 
-3. We encourage everybody with an active BBB account to use this platform instead of third parties or closed source platforms.
+3. We encourage everybody with an active BBB account to use this
+   platform instead of third parties or closed source platforms.
 
-4. To limit security surface area, we will disable accounts that haven't logged in during the past 6 months. Accounts can always be re-enabled when people want to use them again.
+4. To limit security surface area, we will disable accounts that
+   haven't logged in during the past 6 months. Accounts can always be
+   re-enabled when people want to use them again.
 
-5. Every member can have maximum 5 conference rooms, and this limit is enforced by the platform.
+5. Every member can have maximum 5 conference rooms, and this limit is
+   enforced by the platform.
 
-6. The best way to arrange a user account is to get an existing Tor Core Contributor to vouch for the partner. New accounts should be requested by email: training@torproject.org. 
+6. The best way to arrange a user account is to get an existing Tor
+   Core Contributor to vouch for the partner. New accounts should be
+   requested by email at <training@torproject.org>.
 
-7. An account will be closed in the case of: a) end of partnership between Tor Project and the partner, b) violation of Tor Project’s code of conduct, c) violation of this policy, or d) end of the sponsorship of this platform.
+7. An account will be closed in the case of:
 
-8. The account member is responsible for keeping the platform secure and a welcome environment. Therefore, the platform shall not be used by others third parties without the explicit consent of the account holder.
+   a. end of partnership between Tor Project and the partner,
+   b. or violation of Tor Project’s code of conduct,
+   c. or violation of this policy,
+   d. or end of the sponsorship of this platform
 
-9. Every member is free to run private meetings, training, meetups and small conferences.
+8. The account member is responsible for keeping the platform secure
+   and a welcome environment. Therefore, the platform shall not be
+   used by others third parties without the explicit consent of the
+   account holder.
 
-10. As this is a shared service, we might adapt this policy in the future to better accommodate all the participants and our limited resource.
+9. Every member is free to run private meetings, training, meetups and
+   small conferences.
+
+10. As this is a shared service, we might adapt this policy in the
+    future to better accommodate all the participants and our limited
+    resource.
 
 ## Issues