diff --git a/content/en/blog/_posts/2019-02-12-building-a-kubernetes-edge-control-plane-for-envoy-v2.md b/content/en/blog/_posts/2019-02-12-building-a-kubernetes-edge-control-plane-for-envoy-v2.md
index 2749a56a891..feea751e851 100644
--- a/content/en/blog/_posts/2019-02-12-building-a-kubernetes-edge-control-plane-for-envoy-v2.md
+++ b/content/en/blog/_posts/2019-02-12-building-a-kubernetes-edge-control-plane-for-envoy-v2.md
@@ -68,7 +68,7 @@ We started by restructuring the Ambassador internals more along the lines of a m
 
 As we started working more closely with Envoy v2, a testing challenge was quickly identified. As more and more features were being supported in Ambassador, more and more bugs appeared in Ambassador's handling of less common but completely valid combinations of features. This drove to creation of a new testing requirement that meant Ambassador's test suite needed to be reworked to automatically manage many combinations of features, rather than relying on humans to write each test individually. Moreover, we wanted the test suite to be fast in order to maximize engineering productivity.
 
-Thus, as part of the Ambassador rearchitecture, we introduced the [Kubernetes Acceptance Test (KAT)](https://github.com/datawire/ambassador/tree/master/kat) framework. KAT is an extensible test framework that:
+Thus, as part of the Ambassador rearchitecture, we introduced the [Kubernetes Acceptance Test (KAT)](https://github.com/datawire/ambassador/tree/master/python/kat) framework. KAT is an extensible test framework that:
 
 
 
diff --git a/content/en/blog/_posts/2019-03-22-e2e-testing-for-everyone.md b/content/en/blog/_posts/2019-03-22-e2e-testing-for-everyone.md
index 3dcb320736f..462d2bcba41 100644
--- a/content/en/blog/_posts/2019-03-22-e2e-testing-for-everyone.md
+++ b/content/en/blog/_posts/2019-03-22-e2e-testing-for-everyone.md
@@ -301,7 +301,7 @@ in a `BeforeEach` for each test and freed in an `AfterEach`. It has a
 which can be used by a test.
 
 The [PMEM-CSI storage
-test](https://github.com/intel/pmem-csi/blob/586ae281ac2810cb4da6f1e160cf165c7daf0d80/storage/csi_volumes.go#L51)
+test](https://github.com/intel/pmem-csi/blob/devel/test/e2e/storage/csi_volumes.go#L51)
 imports the Kubernetes storage test suite and sets up one instance of
 the provisioning tests for a PMEM-CSI driver which must be already
 installed in the test cluster. The storage test suite changes the