From 590258794a71b05c95a645f49ebfa8982a057f40 Mon Sep 17 00:00:00 2001 From: Kaslin Fields Date: Tue, 30 Jun 2020 09:47:33 -0700 Subject: [PATCH] Update "blog" to tutorial Co-authored-by: Tim Bannister --- .../en/blog/_posts/2020-06-30-SIG-Windows-Spotlight/index.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/en/blog/_posts/2020-06-30-SIG-Windows-Spotlight/index.md b/content/en/blog/_posts/2020-06-30-SIG-Windows-Spotlight/index.md index 2872ba287f..addb059a06 100644 --- a/content/en/blog/_posts/2020-06-30-SIG-Windows-Spotlight/index.md +++ b/content/en/blog/_posts/2020-06-30-SIG-Windows-Spotlight/index.md @@ -36,7 +36,7 @@ So when it comes to running containers on Windows, there are actually two very i * Native Windows processes running as native Windows Server style containers, * and traditional Linux containers running on a Linux Kernel, generally hosted on a lightweight Hyper-V Virtual Machine. -You can learn more about Linux and Windows containers in [this blog from Microsoft](https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/linux-containers). +You can learn more about Linux and Windows containers in this [tutorial](https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/linux-containers) from Microsoft. @@ -102,4 +102,3 @@ As a closing message from SIG-Windows: *** #### _"We welcome you to get involved and join our community to share feedback and deployment stories, and contribute to code, docs, and improvements of any kind."_ *** -