diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
index 6e60096c1..fff2ae5dd 100644
--- a/.github/CONTRIBUTING.md
+++ b/.github/CONTRIBUTING.md
@@ -29,7 +29,7 @@ Here's a high level process for submitting new samples or updates to existing on
 2. Fork the main repository to your GitHub account
 3. Create a new branch for your fork for the contribution based on dev branch
 4. Include your changes to your branch
-5. Commit your changes using descriptive commit message - These are used to track changes on the repositories for monthly communications, see [September 2016](dev.office.com/blogs/PnP-September-2016-Release) as an example
+5. Commit your changes using descriptive commit message - These are used to track changes on the repositories for monthly communications, see [May 2017](https://dev.office.com/blogs/PnP-May-2017-Release) as an example
 6. Create a pull request in your own fork and target 'dev' branch
 7. Fill up the provided PR template with the requested details
 
diff --git a/README.md b/README.md
index 3f08dab94..189f26f89 100644
--- a/README.md
+++ b/README.md
@@ -2,7 +2,7 @@
 
 This repository contains the samples that demonstrate different usage patterns for the SharePoint Framework client-side web parts.
 
-SharePoint client-side web parts are controls that appear inside a SharePoint page but run locally in the browser. They're the building blocks of pages that appear on a SharePoint site. You can build client-side web parts using modern script development tools and the SharePoint workbench (a development test surface), and you can deploy your client-side web parts to classic web part pages in Office 365 Developer tenants. In addition to plain JavaScript projects, you can build web parts alongside common scripting frameworks, such as AngularJS and React. For example, you can use React along with components from Office UI Fabric React to quickly create experiences based on the same components used in Office 365
+SharePoint client-side web parts are controls that appear inside a SharePoint page but run locally in the browser. They're the building blocks of pages that appear on a SharePoint site. You can build client-side web parts using modern script development tools and the SharePoint workbench (a development test surface), and you can deploy your client-side web parts to classic web part pages in Office 365 tenants. In addition to plain JavaScript projects, you can build web parts alongside common scripting frameworks, such as AngularJS and React. For example, you can use React along with components from Office UI Fabric React to quickly create experiences based on the same components used in Office 365
 
 # Additional resources
 
diff --git a/samples/README-template.md b/samples/README-template.md
index 2006a08f9..ba15fc293 100644
--- a/samples/README-template.md
+++ b/samples/README-template.md
@@ -10,7 +10,7 @@ Short summary on functionality and used technologies.
 
 ## Applies to
 
-* [SharePoint Framework](https://blogs.office.com/2017/02/23/sharepoint-framework-reaches-general-availability-build-and-deploy-engaging-web-parts-today/)
+* [SharePoint Framework](https:/dev.office.com/sharepoint)
 * [Office 365 tenant](https://dev.office.com/sharepoint/docs/spfx/set-up-your-development-environment)
 
 > Update accordingly as needed.