Update intro_sheet.md' formatting somewhat more.

diff --git a/intro_sheet.md b/intro_sheet.md
index c10f72ad3f4ce1ebb18c07fdb9c46ffd9af4f534..e3de97d7cb65a7fd61ac93f17517227febed4ccc 100644 (file)
--- a/intro_sheet.md
+++ b/intro_sheet.md
@@ -5,13 +5,15 @@ Intro Sheet for new Technical Committee Members
 
 ## Constitution §6
 
-§6 from the constitution is our bible for how we're supposed to work publicly
+[§6](https://www.debian.org/devel/constitution#item-6) from the constitution is
+our bible for how we're supposed to work publicly
 
 ## Standard Resolution Procedure (§6.3.1)
 
-We use the standard resolution procedure (§6.3.1) using Don's pocket-devotee
-script, which allows us to get condorcet voting in shell. Please use the `><=`
-format for expressing your votes.
+We use the standard resolution procedure
+[§6.3.1](https://www.debian.org/devel/constitution#item-6) using Don's
+pocket-devotee script, which allows us to get condorcet voting in shell. Please
+use the `><=` format for expressing your votes.
 
 e.g.
 ```
@@ -22,20 +24,23 @@ A > B = C > D = E = F
 
 ## Public mailing list
 
-Make sure you are subscribed to debian-ctte@lists.debian.org, the public
+Make sure you are subscribed to
+[debian-ctte@lists.debian.org](mailto:debian-ctte@lists.debian.org), the public
 mailing list where all public matters are discussed.
 
 ## Private alias
 
 We have a private alias which you'll get subscribed to:
-debian-ctte-private@debian.org which we should be making use of when needed. By
-default we should work publically, but for all sensitive things, keep the
-private list in explicit CC. It's good for the parties we're privately talking
-to for them to know that the rest of the TC is in the loop, as well for our
-archival.
+[debian-ctte-private@debian.org](mailto:debian-ctte-private@debian.org) which we
+should be making use of when needed. By default we should work publically, but
+for all sensitive things, keep the private list in explicit CC. It's good for
+the parties we're privately talking to for them to know that the rest of the TC
+is in the loop, as well for our (personal) archival.
 
 ## tech-ctte pseudo-bug
 
+https://bugs.debian.org/tech-ctte
+
 Beware of list-vs-bug mails; we try to have all issues separated in bug
 reports, which get to the list; so for non-meta discussions, we should always
 only write to the bug.
@@ -53,8 +58,9 @@ https://anonscm.debian.org/git/collab-maint/debian-ctte.git
 
 ## Shared calendar
 
-The git repository contains a meetings.ics calendar file to list the future
-meetings, both IRC and IRL.
+The git repository contains a
+[meetings.ics](https://salsa.debian.org/debian/tech-ctte/raw/master/meetings.ics)
+calendar file to list the future meetings, both IRC and IRL.
 
 # Principles