docs: fix typos (#1039)

Author: hishamhm

docs/src/functions.md

@@ -4,7 +4,7 @@ Functions in Teal should work like you expect, and we have already showed
 various examples.
 
 You can declare nominal function types, like we do for records, to avoid
-longwinded type declarations, especially when declaring functions that take
+long-winded type declarations, especially when declaring functions that take
 callbacks. This is done with using `function` types, and they can be generic as
 well:
 

docs/src/interfaces.md

@@ -6,7 +6,7 @@ A concrete record is a type declared with `record`, which can be used
 both as a Lua table and as a type. In object-oriented terms, the record
 itself works as class whose fields work as class attributes,
 while other tables declared with the record type are objects whose
-fields are object atributes. For example:
+fields are object attributes. For example:
 
 ```lua
 local record MyConcreteRecord

docs/src/macroexp.md

@@ -100,6 +100,6 @@ end
 ```
 
 At this time, macroexp declarations within records do not allow inference,
-so the `function` type needs to be explicitly declared when implementinga
+so the `function` type needs to be explicitly declared when implementing a
 a field or metamethod as a `macroexp`. This requirement may be dropped in
 the future.

docs/src/metamethods.md

@@ -40,7 +40,7 @@ print((r + s).x)      -- prints 32
 ```
 
 Note that we explicitly declare variables as `Rec` when initializing the
-declaration with `setmetatable`. The Teal standard library definiton of
+declaration with `setmetatable`. The Teal standard library definition of
 `setmetatable` is `function<T>(T, metatable<T>): T`, so declaring the correct
 record type in the declaration assigns the record type to the type variable
 `T` in the return value of the function call, causing it to propagate to the