From c4001937eabb81211adfe12a57ca5a940ec6454d Mon Sep 17 00:00:00 2001 From: Daniel Canter Date: Wed, 27 Apr 2022 00:45:05 -0700 Subject: [PATCH] Fix wrong word use Manor -> manner Signed-off-by: Daniel Canter --- internal/layers/layers.go | 2 +- .../github.com/Microsoft/hcsshim/internal/layers/layers.go | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/internal/layers/layers.go b/internal/layers/layers.go index e0fa566b63..c8e40edc2a 100644 --- a/internal/layers/layers.go +++ b/internal/layers/layers.go @@ -87,7 +87,7 @@ func MountContainerLayers(ctx context.Context, containerID string, layerFolders } path := layerFolders[len(layerFolders)-1] rest := layerFolders[:len(layerFolders)-1] - // Simple retry loop to handle some behavior on RS5. Loopback VHDs used to be mounted in a different manor on RS5 (ws2019) which led to some + // Simple retry loop to handle some behavior on RS5. Loopback VHDs used to be mounted in a different manner on RS5 (ws2019) which led to some // very odd cases where things would succeed when they shouldn't have, or we'd simply timeout if an operation took too long. Many // parallel invocations of this code path and stressing the machine seem to bring out the issues, but all of the possible failure paths // that bring about the errors we have observed aren't known. diff --git a/test/vendor/github.com/Microsoft/hcsshim/internal/layers/layers.go b/test/vendor/github.com/Microsoft/hcsshim/internal/layers/layers.go index e0fa566b63..c8e40edc2a 100644 --- a/test/vendor/github.com/Microsoft/hcsshim/internal/layers/layers.go +++ b/test/vendor/github.com/Microsoft/hcsshim/internal/layers/layers.go @@ -87,7 +87,7 @@ func MountContainerLayers(ctx context.Context, containerID string, layerFolders } path := layerFolders[len(layerFolders)-1] rest := layerFolders[:len(layerFolders)-1] - // Simple retry loop to handle some behavior on RS5. Loopback VHDs used to be mounted in a different manor on RS5 (ws2019) which led to some + // Simple retry loop to handle some behavior on RS5. Loopback VHDs used to be mounted in a different manner on RS5 (ws2019) which led to some // very odd cases where things would succeed when they shouldn't have, or we'd simply timeout if an operation took too long. Many // parallel invocations of this code path and stressing the machine seem to bring out the issues, but all of the possible failure paths // that bring about the errors we have observed aren't known.