fix broken links from foundation repo

website/content/maintainers/community/vendor-neutrality.md

@@ -20,7 +20,7 @@ Many adopters may be interested in commercial support for CNCF projects, but may
 
 ### Websites
 
-* Please refer to the CNCF [website guidelines](https://github.com/cncf/foundation/blob/main/website-guidelines.md)
+* Please refer to the CNCF [website guidelines](https://github.com/cncf/foundation/blob/main/policies-guidance/website-guidelines.md)
 
 ### Blogs
 

website/content/resources/glossary.md

@@ -77,7 +77,7 @@ Lazy consensus is a decision-making principle commonly used in open source commu
 Open Governance refers to a [governance](#governance) model that promotes transparency, inclusivity, and community participation in decision-making processes. Open source projects often adopt open governance to ensure that contributors and community members have a voice in shaping the project's direction. More information about open governance can be found in the [Governance Guide](https://contribute.cncf.io/maintainers/governance/overview/).
 
 ## Open Source License
-An Open Source license is a legal instrument that grants permissions and defines the terms under which others can use, modify, and distribute an open source project or its source code. Licenses ensure that open source projects remain free and accessible while protecting the rights of contributors. CNCF's approved licenses can be found [here](https://github.com/cncf/foundation/blob/main/allowed-third-party-license-policy.md#approved-licenses-for-allowlist).
+An Open Source license is a legal instrument that grants permissions and defines the terms under which others can use, modify, and distribute an open source project or its source code. Licenses ensure that open source projects remain free and accessible while protecting the rights of contributors. CNCF's approved licenses can be found [here](https://github.com/cncf/foundation/blob/main/policies-guidance/allowed-third-party-license-policy.md#approved-licenses-for-allowlist).
 
 ## PR workflow
 PR workflow refers to the process and steps involved in handling Pull Requests (PRs) within an open source project. It typically includes activities such as submitting a PR, code review, addressing feedback, and merging the changes into the project's codebase. More information about PR workflow and how a successful one will look like can be found [here](https://contribute.cncf.io/maintainers/community/contributor-growth-framework/pr-workflow/).

website/content/resources/how-to/submit-license-exception-request.md

@@ -13,7 +13,7 @@ Many CNCF projects may require the use of different licenses for various compone
 Under section 11(g) of the CNCF charter, the CNCF Governing Board is empowered to approve alternative licenses on an exception basis. The Governing Board has taken several steps to facilitate this process:
 
 * utilizing Linux Foundation staff to assist with scanning for license policy issues;
-* implementing [a policy to automatically approve](https://github.com/cncf/foundation/blob/main/allowed-third-party-license-policy.md) third-party components meeting certain criteria; and
+* implementing [a policy to automatically approve](https://github.com/cncf/foundation/blob/main/policies-guidance/allowed-third-party-license-policy.md) third-party components meeting certain criteria; and
 * empowering the CNCF Legal Committee, consisting of attorneys from Governing Board member companies, to review and advise the Governing Board on review requests for exceptions where not automatically approved.
 
 # Submitting a license exception request
@@ -23,7 +23,7 @@ If you are a maintainer for a CNCF project that is seeking an exception to the C
 1. First, determine whether a new exception is required at all:
 
   * (a) If your request is for code under Apache-2.0 or documentation under CC-BY-4.0, then no exception should be needed.
-  * (b) If your request is for a component that is entirely covered by the [Approved Licenses for Allowlist](https://github.com/cncf/foundation/blob/main/allowed-third-party-license-policy.md#approved-licenses-for-allowlist), and also meets the other [Allowlist License Policy requirements](https://github.com/cncf/foundation/blob/main/allowed-third-party-license-policy.md#cncf-allowlist-license-policy), then no exception should be needed.
+  * (b) If your request is for a component that is entirely covered by the [Approved Licenses for Allowlist](https://github.com/cncf/foundation/blob/main/policies-guidance/allowed-third-party-license-policy.md#approved-licenses-for-allowlist), and also meets the other [Allowlist License Policy requirements](https://github.com/cncf/foundation/blob/main/policies-guidance/allowed-third-party-license-policy.md#cncf-allowlist-license-policy), then no exception should be needed.
   * (c) If your request is for a third-party component for which a license exception has previously been granted, and the license and intended use of that component have not changed from the prior approval, then no exception should be needed. (see **NOTE** below)
   * (d) If you believe that an exception is required despite the above criteria being satisfied, then please feel free to submit a request anyway, explaining why you believe an exception is required.
 

website/content/resources/project-services/maturity-levels/_index.md

@@ -9,13 +9,13 @@ description: Requestable Marketing resources available to Projects
 
 CNCF provides a full portfolio of marketing services and programs to support community and ecosystem engagement for CNCF projects. This includes:
 
-- [CNCF Online Programs](https://github.com/cncf/foundation/blob/master/online-programs-guidelines.md): Graduated and incubating projects can participate in Online Programs like webinars, videos, and livestream. They can communicate release launch details or provide a project update. The exception is Kubernetes, which holds a webinar approximately 30 days after a release.
+- [CNCF Online Programs](https://github.com/cncf/foundation/blob/main/policies-guidance/online-programs-guidelines.md): Graduated and incubating projects can participate in Online Programs like webinars, videos, and livestream. They can communicate release launch details or provide a project update. The exception is Kubernetes, which holds a webinar approximately 30 days after a release.
 - [CNCF Blog](https://github.com/cncf/foundation/blob/master/blog-guidelines.md) and [Kubernetes.io Blog](https://kubernetes.io/docs/contribute/new-content/blogs-case-studies/): Graduated and incubating projects can submit blog posts. Share technical content and how-to's, stories about cloud native and project deployments, and use cases and success stories. Blog posts should not be vendor pitches. They must contain content that applies broadly to the Kubernetes and cloud native community. The Kubernetes blog receives over 1.5M visits a week.
-- [Case Studies](https://github.com/cncf/foundation/blob/master/case-study-guidelines.md): End-user case studies help elevate the technical conversations to business objectives and challenges. This program features use cases and the impact CNCF project and cloud native technologies are having on end users' businesses. The case studies build narratives around specific metrics that reflect the positive as a resource for companies considering adopting cloud native technologies.
+- [Case Studies](https://github.com/cncf/foundation/blob/main/policies-guidance/case-study-guidelines.md): End-user case studies help elevate the technical conversations to business objectives and challenges. This program features use cases and the impact CNCF project and cloud native technologies are having on end users' businesses. The case studies build narratives around specific metrics that reflect the positive as a resource for companies considering adopting cloud native technologies.
 - [Newsletter](https://lists.cncf.io/g/newsletter/messages): The CNCF newsletter is published monthly. Project updates are a regular feature in the newsletter.
 - CNCF manages the blog editorial calendar for balanced content shared with the community. We also provide writing, editing, and funding freelancers to develop content.
 - Project media velocity reports: Monthly, CNCF pulls press mentions and share of voice data for all projects including mentions in social media and key messaging.
-- [Fashion a Phippy](https://github.com/cncf/foundation/blob/main/phippy-guidelines.md): Graduated projects can donate a character to the [Phippy and Friends](https://www.cncf.io/phippy/) program, to help others better understand the concepts of cloud native computing, and increase the marketing and engagement opportunities for their project.
+- [Fashion a Phippy](https://github.com/cncf/foundation/blob/main/policies-guidance/phippy-guidelines.md): Graduated projects can donate a character to the [Phippy and Friends](https://www.cncf.io/phippy/) program, to help others better understand the concepts of cloud native computing, and increase the marketing and engagement opportunities for their project.
 
 ### Marketing Communications
 
@@ -66,7 +66,7 @@ Projects coming in as Sandbox
 - If the media contacts CNCF regarding the news, CNCF will make an introduction directly to the project.
 - Correct terminology: "Cloud Native Sandbox" or "CNCF Sandbox projects"
 - CNCF does not provide press outreach, a CNCF or TOC briefing, a blog, or a social card
-- Exception: A member may share a blog about any open source project, including a Sandbox project. See the [CNCF blog guidelines](https://github.com/cncf/foundation/blob/master/blog-guidelines.md)
+- Exception: A member may share a blog about any open source project, including a Sandbox project. See the [CNCF blog guidelines](https://github.com/cncf/foundation/blob/main/policies-guidance/blog-guidelines.md)
 
 ### Project launches and new release support