check in community without static

Signed-off-by: Billy Zha <jinzha1@microsoft.com>

versioned_docs/version-next/community/contributing_guide.mdx

@@ -148,7 +148,7 @@ Git has a `-s` command line option to do this automatically:
 If you forgot to do this and have not yet pushed your changes to the remote
 repository, you can amend your commit with the sign-off by running
 
-    git commit --amend -s
+    git commit --amend -s 
 
 ## Pull Request Checklist
 

versioned_docs/version-next/community/contributor_ladder.mdx

@@ -16,21 +16,21 @@ sidebar_position: 40
 
 ## Contributor Ladder
 
-Hello! We are excited that you want to learn more about our project contributor ladder!
-This contributor ladder outlines the different contributor roles within the project,
-along with the responsibilities and privileges that come with them.
+Hello! We are excited that you want to learn more about our project contributor ladder! 
+This contributor ladder outlines the different contributor roles within the project, 
+along with the responsibilities and privileges that come with them. 
 Community members generally start at the first levels of the "ladder" and advance up it as their involvement in the project grows.
 Our project members are happy to help you advance along the contributor ladder.
 
-Each of the contributor roles below is organized into three sections.
-"Responsibilities" are tasks that a contributor is expected to do.
-"Requirements" are qualifications a person needs to meet to be in that role,
+Each of the contributor roles below is organized into three sections. 
+"Responsibilities" are tasks that a contributor is expected to do. 
+"Requirements" are qualifications a person needs to meet to be in that role, 
 and "Privileges" are rights contributors on that level are entitled to.
 
 ### Contributor
-A Contributor directly adds value to the project.
-Contributions need not be code.
-Individuals at the Contributor level may be new contributors,
+A Contributor directly adds value to the project. 
+Contributions need not be code. 
+Individuals at the Contributor level may be new contributors, 
 or they may only contribute occasionally.
 
 * Responsibilities include:
@@ -54,22 +54,22 @@ or they may only contribute occasionally.
 
 ### Owners Structure
 There are two types of owners in the ORAS project hierarchy: organization owners and subproject owners.
-ORAS organization owners oversee the overall project and its health.
-Subproject owners focus on a single repository,
-a group of related repositories,
-a service (e.g., a website),
+ORAS organization owners oversee the overall project and its health. 
+Subproject owners focus on a single repository, 
+a group of related repositories, 
+a service (e.g., a website), 
 or subproject to support the other subprojects (e.g., marketing or community management).
 
-Changes in ORAS Organization owners have to be announced via an
-[issue on the Community repository](https://github.com/oras-project/community/issues).
+Changes in ORAS Organization owners have to be announced via an 
+[issue on the Community repository](https://github.com/oras-project/community/issues). 
 Changes to sub-project owners are to be announced via the appropriate sub-project issue.
 
-You can find more information on the roles of organization owners and
+You can find more information on the roles of organization owners and 
 subproject owners in the [governance](https://github.com/oras-project/community/blob/main/governance/GOVERNANCE.md).
 
 ## Inactivity
-It is important for contributors to be and stay active to set an example and show commitment to the project.
-Inactivity is harmful to the project as it may lead to unexpected delays,
+It is important for contributors to be and stay active to set an example and show commitment to the project. 
+Inactivity is harmful to the project as it may lead to unexpected delays, 
 contributor attrition, and a lost of trust in the project.
 
 * Inactivity is measured by:
@@ -81,24 +81,24 @@ contributor attrition, and a lost of trust in the project.
 
 ## Involuntary Removal or Demotion
 
-Involuntary removal/demotion of a contributor happens when responsibilities and requirements aren't being met.
-This may include repeated patterns of inactivity, extended period of inactivity,
-a period of failing to meet the requirements of your role,
-and/or a violation of the Code of Conduct.
-This process is important because it protects the community and its deliverables while also opens up opportunities for new
+Involuntary removal/demotion of a contributor happens when responsibilities and requirements aren't being met. 
+This may include repeated patterns of inactivity, extended period of inactivity, 
+a period of failing to meet the requirements of your role, 
+and/or a violation of the Code of Conduct. 
+This process is important because it protects the community and its deliverables while also opens up opportunities for new 
 contributors to step in.
 
 Involuntary removal or demotion is handled through a vote by a majority of the current Maintainers.
 
 ## Stepping Down/Emeritus Process
-If and when contributors' commitment levels change,
-contributors can consider stepping down (moving down the contributor ladder) vs moving to emeritus status
+If and when contributors' commitment levels change, 
+contributors can consider stepping down (moving down the contributor ladder) vs moving to emeritus status 
 (completely stepping away from the project).
 
-Contact the Maintainers about changing to Emeritus status,
+Contact the Maintainers about changing to Emeritus status, 
 or reducing your contributor level.
 
 ## Contact
-* For inquiries, please drop a message in the #oras channel in the CNCF Workspace.
-You can follow the instructions in the [community resources](../community/community_resources.mdx#joining-the-slack-channel)
+* For inquiries, please drop a message in the #oras channel in the CNCF Workspace. 
+You can follow the instructions in the [community resources](../community/community_resources.mdx#joining-the-slack-channel) 
 to join it.

versioned_docs/version-next/community/reporting_security_concerns.mdx

@@ -5,7 +5,7 @@ sidebar_position: 50
 
 # Security Policy
 
-Thank you for taking the time to report a security vulnerability.
+Thank you for taking the time to report a security vulnerability. 
 We would like to investigate every report thoroughly.
 
 ## Reporting a Vulnerability
@@ -20,9 +20,9 @@ Navigate to the appropriate reporsitory.
 
 Click on `Security` and then `Report a vulnerability`
 
-![Screenshot of how to report a vulnerability](/img/reporting_a_security_concern.png)
+![Screenshot of how to report a vulnerability](../../static/img/reporting_a_security_concern.png)
 
-**Step 3**
+**Step 3** 
 
 You can fill in all the details of the vulnerability and click on `Submit report`.
 This report will be visible to only the maintainers (and anyone else required to look into the issue).
@@ -40,16 +40,16 @@ Please send us a report whenever you:
 
 The ORAS maintainers will acknowledge and analyze your report within 14 working days for high severity issues.
 
-Any vulnerability information you share with us, stays with the maintainers.
+Any vulnerability information you share with us, stays with the maintainers. 
 We will only disclose the information that is required to resolve the problem.
 
 We will update you on the status of the report throughout.
 
 ## Fixing the issue
 
-Once a security vulnerability has been identified, the maintainers (contributors, if required) will work on finding a solution.
+Once a security vulnerability has been identified, the maintainers (contributors, if required) will work on finding a solution. 
 The development and testing for the fix will happen in a private GitHub repository in order to prevent premature disclosure of the vulnerability.
 
-After the fix has been tested and deemed fit to be made public,
-the changes will be merged from the private GitHub repository to the appropriate public branches.
+After the fix has been tested and deemed fit to be made public, 
+the changes will be merged from the private GitHub repository to the appropriate public branches. 
 All the necessary binaries will be built and published.