fix: typos (#1335)

* Update SECURITY.md

* Update message_buffer.ts

* Update ser.rs

* Let's see

---------

Co-authored-by: Pioua <[email protected]>

Author: guibescos

.github/workflows/ci-message-buffer-idl.yml

@@ -34,9 +34,11 @@ jobs:
         run: anchor build
       - name: Copy anchor target files
         run: cp ./target/idl/message_buffer.json idl/ && cp ./target/types/message_buffer.ts idl/
+      - name: Install prettier globally
+        run: npm install -g [email protected]
       - name: Run prettier (to avoid pre-commit failures)
         run: |
-          npx prettier --write "./idl/*"
+          npx prettier@2.7.1 --write "./idl/*"
       - name: Check IDL changes
         # Fails if the IDL files are not up to date. Please use anchor build to regenerate the IDL files for
         # the current version of the contract and update idl directory.

SECURITY.md

@@ -43,15 +43,15 @@ As these 3rd party audits are completed and issues are sufficiently addressed, w
 
 The Pyth project maintains a social media monitoring program to stay abreast of important ecosystem developments.
 
-These developments include monitoring services like Twitter for key phrases and patterns such that the Pyth project is informed of a compromise or vulnerability in a dependancy that could negatively affect Pyth or its users.
+These developments include monitoring services like Twitter for key phrases and patterns such that the Pyth project is informed of a compromise or vulnerability in a dependency that could negatively affect Pyth or its users.
 
 In the case of a large ecosystem development that requires response, the Pyth project will engage its security incident response program.
 
 ## Incident Response
 
 The Pyth project maintains an incident response program to respond to vulnerabilities or active threats to Pyth, its users, or the ecosystems it's connected to. Pyth can be made aware about a security event from a variety of different sources (eg. bug bounty program, audit finding, security monitoring, social media, etc.)
 
-When a Pyth project contributor becomes aware of a security event, that contributor immediately holds the role of [incident commander](https://en.wikipedia.org/wiki/Incident_commander) for the issue until they hand off to a more appropriate incident commander. A contributor does not need to be a "security person" or have any special priviledges to hold the role of incident commander, they simply need to be responsible, communicate effectively, and maintain the following obligations to manage the incident to completion.
+When a Pyth project contributor becomes aware of a security event, that contributor immediately holds the role of [incident commander](https://en.wikipedia.org/wiki/Incident_commander) for the issue until they hand off to a more appropriate incident commander. A contributor does not need to be a "security person" or have any special privileges to hold the role of incident commander, they simply need to be responsible, communicate effectively, and maintain the following obligations to manage the incident to completion.
 
 The role of the incident commander for Pyth includes the following minimum obligations:
 

pythnet/message_buffer/tests/message_buffer.ts

@@ -535,7 +535,7 @@ describe("message_buffer", () => {
     const messageBufferAccountDataLenBefore =
       messageBufferAccountDataBefore.length;
 
-    // check that header is stil the same as before
+    // check that header is still the same as before
     const messageBufferHeaderBefore = deserializeMessageBufferHeader(
       messageBufferProgram,
       messageBufferAccountDataBefore

pythnet/pythnet_sdk/src/wire/ser.rs

@@ -45,7 +45,7 @@
 //! }
 //! ```
 //!
-//! The macro will expand into (a more complicated but equivelent) version of:
+//! The macro will expand into (a more complicated but equivalent) version of:
 //!
 //! ```rust,ignore
 //! impl serde::Serialize for ExampleEnum {
@@ -76,7 +76,7 @@
 //! any format we desire as long as there is a `Serializer` implementation for it. With aggressive
 //! inlining, the compiler will be able to optimize away the intermediate state objects and calls
 //! to `serialize_field` and `serialize_*_variant` and the final result of our parser will have
-//! very close to equivelent performance to a hand written implementation.
+//! very close to equivalent performance to a hand written implementation.
 //!
 //! The Pyth Serialization Format
 //! ================================================================================
@@ -92,7 +92,7 @@
 //! Integers:
 //!
 //! - `{u,i}8` are serialized as a single byte
-//! - `{u,i}16/32/64/128` are serialized as bytes specified by the parser endianess type param.
+//! - `{u,i}16/32/64/128` are serialized as bytes specified by the parser endianness type param.
 //! - Custom {U,I}128/256 wrappers may be implemented later (similar to Borsh) for better support
 //!   in JS, debugging, logging, etc.
 //!