From f95a3b3a48597cebf9849b84a02cd240fb185b16 Mon Sep 17 00:00:00 2001 From: Eng Zer Jun Date: Thu, 18 Apr 2024 22:37:18 +0800 Subject: [PATCH] html: fix typo in package doc Change-Id: I3cacfadc0396c8ef85addd062d991bb6f5b0483a Reviewed-on: https://go-review.googlesource.com/c/net/+/580035 Auto-Submit: Ian Lance Taylor Reviewed-by: Ian Lance Taylor Commit-Queue: Ian Lance Taylor LUCI-TryBot-Result: Go LUCI Auto-Submit: Damien Neil Reviewed-by: Damien Neil --- html/doc.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/html/doc.go b/html/doc.go index 2466ae3d9a..3a7e5ab176 100644 --- a/html/doc.go +++ b/html/doc.go @@ -104,7 +104,7 @@ tokenization, and tokenization and tree construction stages of the WHATWG HTML parsing specification respectively. While the tokenizer parses and normalizes individual HTML tokens, only the parser constructs the DOM tree from the tokenized HTML, as described in the tree construction stage of the -specification, dynamically modifying or extending the docuemnt's DOM tree. +specification, dynamically modifying or extending the document's DOM tree. If your use case requires semantically well-formed HTML documents, as defined by the WHATWG specification, the parser should be used rather than the tokenizer.