From 5d986d7b60b6ba911cc6d784b01f3476bbbeee08 Mon Sep 17 00:00:00 2001
From: data-douser <70299490+data-douser@users.noreply.github.com>
Date: Fri, 25 Aug 2023 07:00:32 -0600
Subject: [PATCH] Update codeql-library-for-go.rst

Correct a typo in the golang docs.
---
 docs/codeql/codeql-language-guides/codeql-library-for-go.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/codeql/codeql-language-guides/codeql-library-for-go.rst b/docs/codeql/codeql-language-guides/codeql-library-for-go.rst
index 33468ab7a71..ab8c7bf65af 100644
--- a/docs/codeql/codeql-language-guides/codeql-library-for-go.rst
+++ b/docs/codeql/codeql-language-guides/codeql-library-for-go.rst
@@ -275,7 +275,7 @@ Entities and name binding
 Not all elements of a code base can be represented as AST nodes. For example, functions defined in
 the standard library or in a dependency do not have a source-level definition within the source code
 of the program itself, and built-in functions like ``len`` do not have a definition at all. Hence
-functions cannot simplify be identified with their definition, and similarly for variables, types,
+functions cannot simply be identified with their definition, and similarly for variables, types,
 and so on.
 
 To smooth over this difference and provide a unified view of functions no matter where they are