Update links from .adoc to .md

Previously we had renamed some pages from .adoc to .md, which broke
some links. I've updated the links for the project_proposals.adoc and
graduation_criteria.adoc to use the new extension, .md.

Signed-off-by: Carolyn Van Slyck <[email protected]>

.github/ISSUE_TEMPLATE/annual-review-template.md

@@ -15,4 +15,4 @@ Your annual review should answer the following questions:
 [] How has the project performed against its goals since the last review? (We won't penalize you if your goals changed for good reasons.)
 [] What are the current goals of the project? For example, are you working on major new features? Or are you concentrating on adoption or documentation?
 [] How can the CNCF help you achieve your upcoming goals?
-[] Do you think that your project meets the criteria for [incubation](https://github.com/cncf/toc/blob/main/process/graduation_criteria.adoc#incubating-stage)?
+[] Do you think that your project meets the criteria for [incubation](https://github.com/cncf/toc/blob/main/process/graduation_criteria.md#incubating-stage)?

.github/ISSUE_TEMPLATE/project-onboarding.md

@@ -12,7 +12,7 @@ We would like to complete onboarding within one month of acceptance.
 
 From the project side, please ensure that you:
 
-- [ ] Understand the project proposal process and reqs: <https://github.com/cncf/toc/blob/main/process/project_proposals.adoc#introduction>
+- [ ] Understand the project proposal process and reqs: <https://github.com/cncf/toc/blob/main/process/project_proposals.md#introduction>
 - [ ] Understand the services available for your project at CNCF <https://www.cncf.io/services-for-projects/>
 - [ ] Ensure your project meets the CNCF IP Policy: <https://github.com/cncf/foundation/blob/master/charter.md#11-ip-policy>
 - [ ] Review the online programs guidelines: <https://github.com/cncf/foundation/blob/master/online-programs-guidelines.md>

CONTRIBUTING.md

@@ -4,7 +4,7 @@
 
 If you're interested in contributing a project to CNCF, please open up an issue here for discussion: https://github.com/cncf/toc/issues
 
-The full project proposal process is located [here](https://github.com/cncf/toc/blob/main/process/project_proposals.adoc).
+The full project proposal process is located [here](https://github.com/cncf/toc/blob/main/process/project_proposals.md).
 
 ## TOC Contributors
 

FAQ.md

@@ -23,7 +23,7 @@ https://github.com/cncf/toc/tree/main/tags
 
 CNCF does not require its hosted projects to follow any specific governance model by default.
 
-Instead, CNCF [specifies](https://github.com/cncf/toc/blob/main/process/graduation_criteria.adoc) that graduated projects need to "[e]xplicitly define a project governance and committer process." 
+Instead, CNCF [specifies](https://github.com/cncf/toc/blob/main/process/graduation_criteria.md) that graduated projects need to "[e]xplicitly define a project governance and committer process." 
 
 This varied and [open governance](https://github.com/opengovernance/opengovernance.dev) approach has led to different projects defining what is best and optimized for their community: 
 
@@ -43,7 +43,7 @@ Neither the CNCF Governing Board (GB) nor the Technical Oversight Committee (TOC
 
 Instead, the maintainers of those projects manage them; this includes defining the governance process. The GB is responsible for the budget.
 
-TOC members are available to provide guidance and conflict resolution if desired to the projects but do not control them. The TOC also helps mature projects through the various CNCF project maturity levels to ensure projects meet the expected [graduation criteria](https://github.com/cncf/toc/blob/main/process/graduation_criteria.adoc). To date, we have had no meaningful disagreements between the TOC and project maintainers.
+TOC members are available to provide guidance and conflict resolution if desired to the projects but do not control them. The TOC also helps mature projects through the various CNCF project maturity levels to ensure projects meet the expected [graduation criteria](https://github.com/cncf/toc/blob/main/process/graduation_criteria.md). To date, we have had no meaningful disagreements between the TOC and project maintainers.
 
 Please see the [TOC Principles](https://github.com/cncf/toc/blob/main/PRINCIPLES.md) for more details.
 

PRINCIPLES.md

@@ -38,7 +38,7 @@ In the GitHub era, open projects are able to get a lot “done” without outsid
 - But: we do not want to impose bureaucracy on projects because that will slow them down.
 - Minimal viable governance also means that the TOC does not step in at a tactical level to overrule project leads’ decisions.
 - There are some basics like [Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md) - see Draft Statement below. Including dealing with problematic leads & maintainers.
-- There is a formal & regulated system of [Graduation Criteria](https://github.com/cncf/toc/blob/main/process/graduation_criteria.adoc) for CNCF Projects
+- There is a formal & regulated system of [Graduation Criteria](https://github.com/cncf/toc/blob/main/process/graduation_criteria.md) for CNCF Projects
 - The TOC/CNCF want the ability to intervene if things go really wrong - i.e., project leads are stuck and cannot fix things.
 - Provide a template for new projects, a set of best practices to help jump-start the task of setting up a new project.
 
@@ -55,7 +55,7 @@ _Principle: Great projects already have many ingredients to succeed. First: do n
 Identify projects that have a real shot at being a useful tool in the evolving box of cloud native technology. This is a mix of mature and early-stage projects. Early stage may not have all the criteria we want: diverse contributor bases, formalized governance, interoperability, cloud-native designs, quality bar, etc. 
 
 Some considerations:
-- Transparent, consistent technical and governance quality bar for [graduation](/process/graduation_criteria.adoc) from incubation
+- Transparent, consistent technical and governance quality bar for [graduation](/process/graduation_criteria.md) from incubation
 - Has users, preferably in production; is a high quality, high-velocity project (for incubation and graduated projects). Inception level projects are targeted at earlier-stage projects to cultivate a community/technology
 - Has a committed and excited team that appears to understand the challenges ahead and wishes to meet them
 - Has a fundamentally sound design without obvious critical compromises that will inhibit potential widespread adoption

process/archiving.md

@@ -27,4 +27,4 @@ What does archiving for a CNCF project mean?
 
 ## Reactivating an Archived Project
 
-Any project can be reactivated into CNCF by following the normal project [proposal](https://github.com/cncf/toc/blob/main/process/project_proposals.adoc) and/or [sandbox](https://github.com/cncf/toc/blob/main/process/sandbox.md) process.
+Any project can be reactivated into CNCF by following the normal project [proposal](https://github.com/cncf/toc/blob/main/process/project_proposals.md) and/or [sandbox](https://github.com/cncf/toc/blob/main/process/sandbox.md) process.

process/due-diligence-guidelines.md

@@ -19,7 +19,7 @@ inclusion of each project at the relevant time.
 To enable the voting TOC members to cast an informed vote about a
 project, it is crucial that each member is able to form their own
 opinion as to whether and to what extent the project meets the agreed
-upon [criteria](https://github.com/cncf/toc/blob/main/process/graduation_criteria.adoc) for
+upon [criteria](https://github.com/cncf/toc/blob/main/process/graduation_criteria.md) for
 sandbox, incubation, or graduation. As the leader of a DD, your job
 is to make sure that they have whatever information they need,
 succinctly and readily available, to form that opinion.
@@ -35,7 +35,7 @@ validity are ideally resolved, helps to foster this consensus.
 
 * Make sure you are clear on the [TOC Principles](https://github.com/cncf/toc/blob/main/PRINCIPLES.md),
  the [project proposal process](https://github.com/cncf/toc/blob/main/process/project_proposals.md),
- the [graduation criteria](https://github.com/cncf/toc/blob/main/process/graduation_criteria.adoc),
+ the [graduation criteria](https://github.com/cncf/toc/blob/main/process/graduation_criteria.md),
  and the [desired cloud native properties](https://www.cncf.io/about/charter/). The project sponsor (a member
  of the TOC) should have assisted in crafting the proposal to explain why it is a good fit for the CNCF. If anything is
  unclear to you, reach out to the project sponsor or, failing that, the TOC mailing list for advice.
@@ -44,12 +44,12 @@ validity are ideally resolved, helps to foster this consensus.
  Consider holding off on commenting on the PR until you have completed the next three steps.
 * Take a look at some [previous submissions](https://github.com/cncf/toc/pulls?utf8=%E2%9C%93&q=is%3Apr)
  (both successful and unsuccessful) to help calibrate your expectations.
-* Verify that all of the basic [project proposal requirements](https://github.com/cncf/toc/blob/main/process/project_proposals.adoc) have been provided.
+* Verify that all of the basic [project proposal requirements](https://github.com/cncf/toc/blob/main/process/project_proposals.md) have been provided.
 * Do as much reading up as you need to (and consult with experts in the specific field) in order to familiarize yourself with the technology
  landscape in the immediate vicinity of the project (and do not only use the proposal and that project's documentation as a guide in this regard).
 * At this point, you should have a very clear technical idea of what exactly the project actually does and does not do, roughly how it compares with and differs from
  similar projects in its technology area, and/or a set of unanswered questions in those regards.
-* Go through the [graduation criteria](https://github.com/cncf/toc/blob/main/process/graduation_criteria.adoc) and for each item,
+* Go through the [graduation criteria](https://github.com/cncf/toc/blob/main/process/graduation_criteria.md) and for each item,
  decide for yourself whether or not you have enough information to make a strong, informed call on that item.
  * If so, write it down, with motivation.
  * If not, jot down what information you feel you are missing.
@@ -91,7 +91,7 @@ the detail where necessary.
 
 #### Project
 
-The key high-level questions that the voting TOC members will be looking to have answered are (from the [graduation criteria](https://github.com/cncf/toc/blob/main/process/graduation_criteria.adoc)):
+The key high-level questions that the voting TOC members will be looking to have answered are (from the [graduation criteria](https://github.com/cncf/toc/blob/main/process/graduation_criteria.md)):
 
 * Do we believe this is a growing, thriving project with committed contributors?
 * Is it aligned with CNCF's values and mission?

process/sandbox-annual-review.md

@@ -37,7 +37,7 @@ Your annual review should answer the following questions:
 * How has the project performed against its goals since the last review? (We won't penalize you if your goals changed for good reasons.)
 * What are the current goals of the project? For example, are you working on major new features? Or are you concentrating on adoption or documentation? 
 * How can the CNCF help you achieve your upcoming goals? 
-* Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/main/process/graduation_criteria.adoc#incubating-stage)? 
+* Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/main/process/graduation_criteria.md#incubating-stage)? 
 
 
 

proposals/pull_request_template.md

@@ -1,7 +1,7 @@
 Thank you for submitting your project proposal to CNCF!
 
 Before you submit your project, please ensure that:
-- [ ] Understand the project proposal process and reqs: https://github.com/cncf/toc/blob/master/process/project_proposals.adoc#introduction
+- [ ] Understand the project proposal process and reqs: https://github.com/cncf/toc/blob/master/process/project_proposals.md#introduction
 - [ ] Understand the services available for your project at CNCF https://www.cncf.io/services-for-projects/
 - [ ] Ensure your project meets the CNCF IP Policy: https://github.com/cncf/foundation/blob/master/charter.md#11-ip-policy
 - [ ] Has your project adopted open governing already? see http:https://opengovernance.dev