Merge pull request #272 from finos/maturity-checklist-fixes

Fixed 2 pages
finos · May 22, 2024 · 24b2357 · 24b2357
2 parents 6236db8 + 9b78c6c
commit 24b2357
Show file tree

Hide file tree

Showing 2 changed files with 0 additions and 10 deletions.
diff --git a/docs/bok/Activities/Level-3/Making-The-Case.md b/docs/bok/Activities/Level-3/Making-The-Case.md
@@ -257,8 +257,3 @@ One argument against [having an OSPO](../Level-2/Creating-An-OSPO) is the cost.
 - **Sharing Cost**: Working on open source projects should mean that cost is amortised amongst the collaborating organisations.
 
 </BoxOut>
-
-
-## Maturity Checklist
-
-<ArticleChecklist checklist={frontMatter.checklist} title={frontMatter.title} />
diff --git a/docs/bok/Activities/Level-5/Why-To-Create-A-Project.md b/docs/bok/Activities/Level-5/Why-To-Create-A-Project.md
@@ -82,8 +82,3 @@ If you using open source it is likely you will use standard open source tooling
 
  * Good examples for this are [FDC3](https://fdc3.finos.org), [Legend](https://legend.finos.org), [Morphir](https://morphir.finos.org) and (the best example) [the Common Domain Model](https://github.com/finos/common-domain-model).
  * Teams working with these technologies and contributing to them learn the standard GitHub Actions/CI model, and are more likely to end up bringing back knowledge of these methods to internal development teams too.
-
-
-## Maturity Checklist
-
-<ArticleChecklist checklist={frontMatter.checklist} title={frontMatter.title} />