mattmakai
diff --git a/‎content/pages/05-deployment/38-serverless.markdown‎
Lines changed: 2 additions & 2 deletions b/‎content/pages/05-deployment/38-serverless.markdown‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎content/pages/05-deployment/39-aws-lambda.markdown‎
Lines changed: 0 additions & 9 deletions b/‎content/pages/05-deployment/39-aws-lambda.markdown‎
Lines changed: 0 additions & 9 deletions
diff --git a/‎content/pages/06-devops/00-devops.markdown‎
Lines changed: 7 additions & 7 deletions b/‎content/pages/06-devops/00-devops.markdown‎
Lines changed: 7 additions & 7 deletions
@@ -58,8 +58,8 @@ and not all of them have Python support.
   [Apache OpenWhisk](https://github.com/openwhisk/openwhisk)
   open source project.
 
-* [Google Cloud Functions](/google-cloud-functions.html) currently
-  only supports JavaScript code execution.
+* [Google Cloud Functions](/google-cloud-functions.html) has
+  [native Python 3.x runtimes](https://cloud.google.com/functions/docs/concepts/python-runtime).
 
 * [Webtask.io](https://webtask.io/) started as a JavaScript service but
   now also has a Python runtime as well.
 
@@ -52,10 +52,6 @@ has support for both Python 2.7, 3.6 and 3.7.
   provides a screen capture of one developer deploying their
   application to Lambda.
 
-* [Automated SQL Injection Testing of Serverless Functions On a Shoestring Budget (and Some Good Music)](https://www.puresec.io/blog/automated-sql-injection-testing-of-serverless-functions-on-a-shoestring-budget-and-some-good-music)
-  is an awesome operational security post that uses Python to test
-  for SQL injection vulnerabilities in serverless functions on AWS Lambda.
-
 * [Building Scikit-Learn For AWS Lambda](https://serverlesscode.com/post/scikitlearn-with-amazon-linux-container/)
   follows up on the 
   [Using Scikit-Learn In AWS Lambda](https://serverlesscode.com/post/deploy-scikitlearn-on-lamba/)
@@ -76,11 +72,6 @@ has support for both Python 2.7, 3.6 and 3.7.
   guide created by a developer who used all of these bits to learn
   AWS services herself.
 
-* [AWS Lambda Serverless Reference Architectures](http://www.allthingsdistributed.com/2016/06/aws-lambda-serverless-reference-architectures.html)
-  provides blueprints with diagrams of common architecture patterns that
-  developers use for their mobile backend, file processing, stream
-  processing and web application projects.
-
 * [Security Overview of AWS Lambda](https://d1.awsstatic.com/whitepapers/Overview-AWS-Lambda-Security.pdf)
   (PDF file) covers their "Shared Responsibility Model" for security and
   compliance. Although the paper bills itself as an in-depth look at 
 
@@ -35,8 +35,8 @@ tools and services for DevOps environments.
   which when used properly can enable continuous software delivery.
 
 * For an Atlassian-centric perspective on tooling, take a look at 
-  this post on how to
-  [choose the right DevOps tools](http://blogs.atlassian.com/2016/03/how-to-choose-devops-tools/)
+  this guide on how to
+  [choose the right DevOps tools](https://www.atlassian.com/devops/devops-tools)
   which is biased towards their tools but still has some good insight
   such as using automated testing to provide immediate awareness of 
   defects that require fixing.
@@ -47,18 +47,18 @@ The following resources give advice and approaches for building the right
 teams, culture, processes and tools into software development organizations.
 
 * [DevOps vs. Platform Engineering](https://alexgaynor.net/2015/mar/06/devops-vs-platform-engineering/)
-  considers DevOps an ad hoc approach to developing software while building
-  a platform is a strict contract. I see this as "DevOps is a process", 
-  while a "platform is code". Running code is better than any organizational 
-  process.
+  considers DevOps to be an ad hoc approach to developing software while 
+  building a platform is a strict contract. I see this as "DevOps is a 
+  process", while a "platform is code". Running code is better than any 
+  organizational process.
 
 * The open source 
   [PagerDuty Incident Response guide](https://response.pagerduty.com/) is the
   amazing result from their company taking the practices they use to keep
   their services running and putting them out for other developers to consume.
   Highly recommended.
 
-* [Introduction to DevOps and Software Delivery Performance](https://www.stridenyc.com/blog/introduction-to-devops-and-software-delivery-performance)
+* [Introduction to DevOps and Software Delivery Performance](https://www.stridenyc.com/blog/devops-and-software-delivery-performance)
   explains the four key delivery metrics of Delivery Lead Time,
   Deployment Frequency, Time to Restore Service, and Change Fail Rate,
   and then gives a high-level overview of technical, process and