From c9c9785345e33bb42d3969a8dac8cf88937b068d Mon Sep 17 00:00:00 2001 From: Michael Vetter Date: Sun, 29 Nov 2020 11:42:06 +0100 Subject: [PATCH] Correct spelling: satisify -> satisfy --- spew/common.go | 2 +- spew/config.go | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/spew/common.go b/spew/common.go index 1be8ce9..ec2a1f7 100644 --- a/spew/common.go +++ b/spew/common.go @@ -100,7 +100,7 @@ func handleMethods(cs *ConfigState, w io.Writer, v reflect.Value) (handled bool) // Choose whether or not to do error and Stringer interface lookups against // the base type or a pointer to the base type depending on settings. // Technically calling one of these methods with a pointer receiver can - // mutate the value, however, types which choose to satisify an error or + // mutate the value, however, types which choose to satisfy an error or // Stringer interface with a pointer receiver should not be mutating their // state inside these interface methods. if !cs.DisablePointerMethods && !UnsafeDisabled && !v.CanAddr() { diff --git a/spew/config.go b/spew/config.go index 2e3d22f..9b8cec2 100644 --- a/spew/config.go +++ b/spew/config.go @@ -59,7 +59,7 @@ type ConfigState struct { // // NOTE: This might be an unsafe action since calling one of these methods // with a pointer receiver could technically mutate the value, however, - // in practice, types which choose to satisify an error or Stringer + // in practice, types which choose to satisfy an error or Stringer // interface with a pointer receiver should not be mutating their state // inside these interface methods. As a result, this option relies on // access to the unsafe package, so it will not have any effect when