Update links and markdown

Author: vivienlacourba

meetings/tpac.md

@@ -1,5 +1,5 @@
 ---
-title: On TPAC Group and Joint-Group Meetings
+title: TPAC Group and Joint-Group Meetings
 toc: true
 ---
 
@@ -16,22 +16,21 @@ In TPAC 2021, since we are still virtual, it will still be challenging to achiev
 Since we'll be virtual, a few reminders:
 
 1. Make sure it's easy for outsiders to discover your meeting. Add your meeting to:
-   
    1. the [TPAC 2021 page](https://www.w3.org/wiki/TPAC/2021/GroupMeetings).
-   2. the [W3C Calendar of the Group](https://www.w3.org/blog/2021/03/group-calendaring-service-enters-beta-test/).
-2. A distributed meeting is one where most of the attendees are expected to participate from remote locations (see [dealing with timezones](organize.html)).
-3. See our [considerations regarding zoom](zoom.html), including recordings and automated meeting transcripts.
-4. If you plan to make a presentation, we recommend you to record them in advance. Ask the events team for assistance if needed but they require 2 weeks lead time (deadline is October 11). See also our [recording tips](https://www.w3.org/wiki/Virtual_Presentations).
-5. Consider if a breakout session might be useful.
+   1. the [W3C Calendar of the Group](https://www.w3.org/blog/2021/group-calendaring-service-enters-beta-test/).
+1. A distributed meeting is one where most of the attendees are expected to participate from remote locations (see [dealing with timezones](organize.md)).
+1. See our [considerations regarding Zoom](zoom.md), including recordings and automated meeting transcripts.
+1. If you plan to make a presentation, we recommend you to record them in advance. Ask the events team for assistance if needed but they require 2 weeks lead time (deadline is October 11). See also our [recording tips](https://www.w3.org/wiki/Virtual_Presentations).
+1. Consider if a breakout session might be useful.
 
-## TPAC Group meeting {#group}
+## TPAC Group Meetings {#group}
 
 TPAC meeting is an opportunity for a Working or Interest Group :
 
 1. look on the progress and goals of the Group as well as the deliverables;
-2. look at related work (e.g in Community Groups) and what's new out there within the scope or related to the Group's mission;
-3. welcome new participants, understand their interests, get their questions/feedback on the Group, and potentially mentor them on how to contribute;
-4. welcome observers, understand their interests in the Group, and get them interested in joining the Group and helping;
+1. look at related work (e.g in Community Groups) and what's new out there within the scope or related to the Group's mission;
+1. welcome new participants, understand their interests, get their questions/feedback on the Group, and potentially mentor them on how to contribute;
+1. welcome observers, understand their interests in the Group, and get them interested in joining the Group and helping;
 
 On the deliverables:
 
@@ -56,11 +55,11 @@ On the deliverables:
 
 ## TPAC Joint Meetings {#joint}
 
-- TPAC is an opportunity for joint meetings between Groups:
+TPAC is an opportunity for joint meetings between Groups:
 
-  1. issues (blocking or otherwise) that you'd be able to advance if you can schedule a joint meeting with another Group, or with representatives from that Group
-  2. horizontal issues raised during wide reviews that have been queued
-  3. requests sent to other Groups that did not progress in there
+1. issues (blocking or otherwise) that you'd be able to advance if you can schedule a joint meeting with another Group, or with representatives from that Group
+1. horizontal issues raised during wide reviews that have been queued
+1. requests sent to other Groups that did not progress in there
 
 ## TPAC Breakouts {#breakout}
 

meetings/transcripts.md

@@ -23,5 +23,5 @@ The Webex Host should make sure Webex Assistant is turned off at the start of a
 
 ## Changelog {#status}
 
-- See [commits history](https://github.com/w3c/Guide/commits/main/meetings/transcripts.html)
+- See [commits history](https://github.com/w3c/Guide/commits/main/meetings/transcripts.md)
 - See also [w3process #334](https://github.com/w3c/process/issues/334)

meetings/workshops.md

@@ -13,7 +13,7 @@ To date, most W3C Workshops have been face-to-face meetings. Going forward, more
 
 ## Proposing a Workshop {#Proposing}
 
-Most workshops to date have been proposed by the W3C Technical Staff, in particular, members of the W3C Strategy Team. Workshops being planned are publicly visible on the [W3C Strategy Funnel](https://github.com/w3c/strategy/projects/2).
+Most workshops to date have been proposed by the W3C Technical Staff, in particular, members of the W3C Strategy Team. Workshops being planned are publicly visible on the [W3C Strategy Team's Incubation Pipeline (Funnel)](https://github.com/orgs/w3c/projects/97).
 
 In the planning phase, each workshop is maintained as an issue on GitHub. For example, here is the issue for the [Inclusive XR workshop](https://github.com/w3c/strategy/issues/175).
 

meetings/zoom.md

@@ -24,7 +24,7 @@ W3C Team account owners should set [account default settings](https://w3c.zoom.u
 - Whiteboard \[on]
 - Show a "Join from your browser" link \[on]
 - When attendees join meeting before host \[off]
-- [Save Captions](transcipts.html) \[off].
+- [Save Captions](transcipts.md) \[off].
 - Attention tracking \[off] ([Zoom says they have removed attention tracking as of 1 April 2020](https://blog.zoom.us/wordpress/2020/04/01/a-message-to-our-users/))
 
 These settings will allow the group to meet even if the Team Host is not present. If an actual Host is required, the Team Host can join the call momentarily and assign co-Host privileges to one or more of the other attendees.
@@ -37,7 +37,7 @@ Zoom offers a [test meeting service](https://zoom.us/test) for anyone to use to
 
 Zoom provides the ability to make recordings. If this feature is used, it must be with the consent of the meeting participants. Chairs have the responsibility to ensure that participants are aware that they are being recorded whenever this feature is used. Recordings are made available after the end (could take a few hours) using an email notification to the meeting host, and can only be shared by default to individuals with a W3C Zoom account. We're looking into providing additional recommendations to make those videos available through other means.
 
-Check also the special guidance on [automated meeting transcripts](transcripts.html).
+Check also the special guidance on [automated meeting transcripts](transcripts.md).
 
 ## Ending a Meeting {#ending}
 
@@ -49,7 +49,7 @@ Participants sometimes wander off and forget to disconnect at the end of a meeti
 
 The standard precautions apply for meeting participants to mute your audio except when you mean to talk to the meeting to avoid interference and accidentally sharing private communications (e.g. yelling at your pets), and also to pay attention to what is visible in your video feed.
 
-Besides the [suggested settings for the W3C team accounts](#suggested-settings), we understand that concerns have been raised regarding the security/privacy of the Zoom clients. Several of the issues reported were based on native application hacks with computers already infected (such as modifying the installation script). The best and most cost-effective way to prevent those issues is to use the Web application for Zoom but it is more CPU intensive. Using an alternative device helps in isolating the native applications or the impact on CPU usage from the Web application. It's the perfect opportunity to repurpose an old device.
+Besides the [suggested settings for the W3C team accounts](#settings), we understand that concerns have been raised regarding the security/privacy of the Zoom clients. Several of the issues reported were based on native application hacks with computers already infected (such as modifying the installation script). The best and most cost-effective way to prevent those issues is to use the Web application for Zoom but it is more CPU intensive. Using an alternative device helps in isolating the native applications or the impact on CPU usage from the Web application. It's the perfect opportunity to repurpose an old device.
 
 ### Zoom documentation {#zoomdoc}
 
@@ -64,7 +64,7 @@ This section provides links to the Zoom documentation.
 - interoperable browser support
 - network bandwidth
 - Native platform independence (a native app that works on Linux, Mac, Windows, …)
-- [privacy](https://zoom.us/privacy?zcid=1231&_ga=2.98581528.769047269.1585831637-830468457.1584135532)
+- [privacy statement](https://www.zoom.com/en/trust/privacy/)
 - queue management
 - reliability
 - scalability