Merge pull request #114 from standard-for-public-code/Reverts-from-companion-to-implementation

Reverts from companion to implementation

Author: jgroenen

README.md

@@ -1,6 +1,6 @@
-# Community built companion to the Standard for Public Code
+# Implementation guide to the Standard for Public Code
 
-This is a repository for guiding implementation choices for the criteria of the [Standard for Public Code](https://standard.publiccode.net), provided by the community.
+This is a repository for guiding implementation choices for the criteria of the [Standard for Public Code](https://standard.publiccode.net).
 
 [![pages-build-deployment](https://github.com/publiccodenet/community-implementation-guide-standard/actions/workflows/pages/pages-build-deployment/badge.svg)](https://github.com/publiccodenet/community-implementation-guide-standard/actions/workflows/pages/pages-build-deployment)
 [![Test](https://github.com/publiccodenet/community-implementation-guide-standard/actions/workflows/test.yml/badge.svg)](https://github.com/publiccodenet/community-implementation-guide-standard/actions/workflows/test.yml)
@@ -19,7 +19,6 @@ If the proposal spans multiple criteria it should be above the list of criteria.
 ### Review of a contributions
 
 Before we merge a pull request of a new or updated proposal, it needs to be reviewed.
-Reviewers should include a codebase steward of the Foundation for Public Code.
 
 ## Problems, suggestions and questions in issues
 

index.md

@@ -1,11 +1,9 @@
-# Community built companion to the Standard for Public Code 0.7.1
+# Implementation guide to the Standard for Public Code 0.7.1
 
-This companion is built with the Community, like the [Community translations](https://publiccodenet.github.io/community-translations-standard/).
-
-It should help when someone asks the question "How can I meet this requirement?" or "What do I need to do to meet this requirement?"
+This guide should help when someone asks the question "How can I meet this requirement?" or "What do I need to do to meet this requirement?"
 
 It can contain examples of implementations, tools, methods that would meet a specific requirement.
-The things that are added should almost be considered to be "pre-approved", meaning that if you were using the guide (and in good spirit) you are almost certain to get a pass when assessed by the Foundation for Public Code.
+The things that are added should almost be considered to be "pre-approved", meaning that if you were using the guide (and in good spirit) you are almost certain to get a pass.
 
 We should keep in mind "there's more than one way to do it": where it makes sense, provide multiple options, especially linking to examples.
 

roadmap.md

@@ -7,6 +7,6 @@
 
 ## Longer term
 
-* Make the workflow of updating the companion after a release of the standard easier
+* Make the workflow of updating the implementation guide after a release of the standard easier
 * Provide examples covering all criteria and their requirements
 * [Bespoke domain name](https://github.com/publiccodenet/community-implementation-guide-standard/issues/81)