docs: fix some typos (#20943)

## Description 

fix some typos

## Test plan 

How did you test the new or updated feature?

---

## Release notes

Check each box that your changes affect. If none of the boxes relate to
your changes, release notes aren't required.

For each box you select, include information after the relevant heading
that describes the impact of your changes that a user might notice and
any actions they must take to implement updates.

- [ ] Protocol: 
- [ ] Nodes (Validators and Full nodes): 
- [ ] gRPC:
- [ ] JSON-RPC: 
- [ ] GraphQL: 
- [ ] CLI: 
- [ ] Rust SDK:

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

external-crates/move/crates/move-binary-format/src/errors.rs

@@ -294,7 +294,7 @@ impl PartialVMError {
         self
     }
 
-    /// Append the message `message` to the message field of the VM status, and insert a seperator
+    /// Append the message `message` to the message field of the VM status, and insert a separator
     /// if the original message is non-empty.
     pub fn append_message_with_separator(
         mut self,

external-crates/move/documentation/book/src/method-syntax.md

@@ -4,7 +4,7 @@ As a syntactic convience, some functions in Move can be called as "methods" on a
 by using the `.` operator to call the function, where the value on the left-hand side of the `.` is
 the first argument to the function (sometimes called the receiver). The type of that value
 statically determines which function is called. This is an important difference from some other
-langauges, where this syntax might indicate a dynamic call, where the function to be called is
+languages, where this syntax might indicate a dynamic call, where the function to be called is
 determined at runtime. In Move, all function calls are statically determined.
 
 In short, this syntax exists to make it easier to call functions without having to create an alias

external-crates/move/documentation/coding_guidelines.md

@@ -207,7 +207,7 @@ impl Foo {
 
 As every integer operation (`+`, `-`, `/`, `*`, etc.) implies edge-cases (e.g. overflows `u64::MAX + 1`, underflows `0u64 -1`, division by zero, etc.),
 we use checked arithmetic instead of directly using math symbols.
-It forces us to think of edge-cases, and handle them explicitely.
+It forces us to think of edge-cases, and handle them explicitly.
 This is a brief and simplified mini guide of the different functions that exist to handle integer arithmetic:
 
 * [checked_](https://doc.rust-lang.org/std/primitive.u32.html#method.checked_add): use this function if you want to handle overflows and underflows as a special edge-case. It returns `None` if an underflow or overflow has happened, and `Some(operation_result)` otherwise.