chore: fix some typos (#58)

Signed-off-by: luchenhan <[email protected]>

book/src/storage/transfer-restrictions.md

@@ -81,6 +81,6 @@ To expand on the example above:
 
 The decision on whether to add the `store` ability to a type should be made carefully. On one hand,
 it is de-facto a requirement for the type to be _usable_ by other applications. On the other hand,
-it allows _wrapping_ and changing the intented storage model. For example, a character may be
-intented to be owned by accounts, but with the `store` ability it can be frozen (cannot be shared -
+it allows _wrapping_ and changing the intended storage model. For example, a character may be
+intended to be owned by accounts, but with the `store` ability it can be frozen (cannot be shared -
 this transition is restricted).

reference/src/method-syntax.md

@@ -32,7 +32,7 @@ coin.value();
 When a method is called, the compiler will statically determine which function is called based on
 the type of the receiver (the argument on the left-hand side of the `.`). The compiler maintains a
 mapping from type and method name to the module and function name that should be called. This
-mapping is created fom the `use fun` aliases that are currently in scope, and from the appropriate
+mapping is created form the `use fun` aliases that are currently in scope, and from the appropriate
 functions in the receiver type's defining module. In all cases, the receiver type is the first
 argument to the function, whether by-value or by-reference.