Update README.md

README.md

@@ -29,21 +29,17 @@ high quality, we request that contributions adhere to the following guidelines.
 - **Provide a link to the application or project’s homepage**. Unless it’s
   extremely popular, there’s a chance the maintainers don’t know about or use
-  the language, framework, editor, app, or project your change applies to.
+  the language or framework.
 - **Provide links to documentation** supporting the change you’re making. If it's
-  possible to provide a build trace, please provide this.
+  possible to provide a link to a successful pipeline on GitLab.com, please 
+  provide this.
 - **Explain why you’re making a change**. Even if it seems self-evident, please
   take a sentence or two to tell us why your change or addition should happen.
   It’s especially helpful to articulate why this change applies to *everyone*
   who works with the applicable technology, rather than just you or your team.
-- **Please consider the scope of your change**. If your change specific to a
-  certain language or framework, then make sure the change is made to the
-  template for that language or framework, rather than to the template for an
-  editor, tool, or operating system.
-
 - **Please only modify *one template* per merge request**. This helps keep merge
   requests and feedback focused on a specific project or technology.
@@ -53,4 +49,4 @@ the more likely we’ll be to accept your contribution quickly.
 Please also understand that we can’t list every tool that ever existed.
 Our aim is to curate a collection of the *most common and helpful* templates,
 not to make sure we cover every project possible. If we choose not to
-include your language, or project, it’s not because it’s not awesome.
+include your language, or framework, it’s not because it’s not awesome.