From 4f78947ac563d78f862c5c8de1c2e1578a8d6e08 Mon Sep 17 00:00:00 2001 From: Mateusz Poliwczak Date: Mon, 29 Jul 2024 20:34:15 +0200 Subject: [PATCH] update Change-Id: I213d00c15f7a6486481ef6677612ea11bccfb91b --- doc/next/6-stdlib/99-minor/encoding/62384.md | 2 +- src/encoding/encoding.go | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/next/6-stdlib/99-minor/encoding/62384.md b/doc/next/6-stdlib/99-minor/encoding/62384.md index fe6bdb4fc4..5b41d4ba6a 100644 --- a/doc/next/6-stdlib/99-minor/encoding/62384.md +++ b/doc/next/6-stdlib/99-minor/encoding/62384.md @@ -2,4 +2,4 @@ Two new interfaces, [TextAppender] and [BinaryAppender], have been introduced to append the textual or binary representation of an object to a byte slice. These interfaces provide the same functionality as [TextMarshaler] and [BinaryMarshaler], but instead of allocating a new slice -each time, they append the data directly to the existing slice +each time, they append the data directly to an existing slice. diff --git a/src/encoding/encoding.go b/src/encoding/encoding.go index 1e7456c0f1..4d288b6d3b 100644 --- a/src/encoding/encoding.go +++ b/src/encoding/encoding.go @@ -36,7 +36,7 @@ type BinaryUnmarshaler interface { } // BinaryAppender is the interface implemented by an object -// that can append the bianry representation of itself. +// that can append the binary representation of itself. // If a type implements both [BinaryAppender] and [BinaryMarshaler], // then v.MarshalBinary() must be semantically identical to v.AppendBinary(nil). type BinaryAppender interface {