Review comments

Signed-off-by: Viktor Söderqvist <[email protected]>

topics/functions-intro.md

@@ -68,10 +68,9 @@ Let's explore Valkey Functions via some tangible examples and Lua snippets.
 
 At this point, if you're unfamiliar with Lua in general and specifically in Valkey, you may benefit from reviewing some of the examples in [Introduction to Eval Scripts](eval-intro.md) and [Lua API](lua-api.md) pages for a better grasp of the language.
 
-Every Valkey function belongs to a single library that's loaded to Valkey.
+Every Valkey function belongs to a library.
 Loading a library to the database is done with the [`FUNCTION LOAD`](../commands/function-load.md) command.
-The command takes the library source code as input and
-the it must start with a Shebang line that provides a metadata about the library, like the language (always "lua") and the library name.
+The library source code must start with a Shebang line that provides metadata about the library, like the language (always "lua") and the library name.
 The Shebang format is:
 
 ```

topics/introduction.md

@@ -36,5 +36,5 @@ It works on most POSIX systems like Linux, \*BSD and MacOS, without external dep
 Linux and MacOS are the two operating systems where Valkey is developed and tested the most, and we **recommend using Linux for deployment**.
 Valkey may work on Solaris-derived systems like Illumos, but support is *best effort*.
 Supported hardware includes x86-64 (AKA amd64), x86 (32-bit) and AArch64 (64-bit ARM).
-It is also know to work on IBM z/Architecture like s390x and builds for this system are available from the Fedora distro.
+It is also known to work on IBM z/Architecture like s390x and builds for this system are available from the Fedora distro.
 There is no official support for Windows builds.