From 03caf4687b02b839ee5b997a9a0931ad43ca9169 Mon Sep 17 00:00:00 2001 From: Nicholas Wilson Date: Mon, 30 Dec 2024 21:00:01 -0600 Subject: [PATCH] Update README.md, fix typos (#200) --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 1bbe880..b052fbc 100644 --- a/README.md +++ b/README.md @@ -106,7 +106,7 @@ Additionally, if you have WSL or WSL2 installed on your desktop, you might want Follow Microsoft's instructions that can be found [here](https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/deploy-containers-on-server#install-docker) -If using the latest edge version of 2019, be prepared to only work in powershell, as it is only a servercore image (no desktop interface). When starting this machine, it will login and go straight to a powershell window. It is reccomended to install text editors and other tools using [Chocolatey](https://chocolatey.org/install). +If using the latest edge version of 2019, be prepared to only work in powershell, as it is only a servercore image (no desktop interface). When starting this machine, it will login and go straight to a powershell window. It is recommended to install text editors and other tools using [Chocolatey](https://chocolatey.org/install). After installing, these commands will work: @@ -120,7 +120,7 @@ docker run hello-world Windows Server 2016 is not able to run Linux images. -Windows Server Build 2004 is capable of running both linux and windows containers simultaneously through Hyper-V isolation. When running containers, use the ```--isolation=hyperv``` command, which will isolate the container using a seperate kernel instance. +Windows Server Build 2004 is capable of running both linux and windows containers simultaneously through Hyper-V isolation. When running containers, use the ```--isolation=hyperv``` command, which will isolate the container using a separate kernel instance. ### Check Version