### Summary of Changes Made: (#1271)

Modular Approach:

Corrected "Singer" to "Signer" in relevant sections.
Fixed grammatical errors: "it look like this" → "it looks like this", "it's dependencies" → "its dependencies".
Removed unnecessary apostrophe in "that's' not swappable".
Adjusted phrasing of the migration process description: "Migration might not be the best word" → "Migration may not be the best word".
Contribution Guide:

Replaced "repo" with "repository" for clarity.
Changed "you have to install Xcode" to "you must install Xcode" for stronger language.
Improved phrasing in the instructions for Linux distribution and Unity website.
Corrected phrasing in the .NET installation instructions using Homebrew.
Made minor updates to provide clearer instructions for adding new modules and linking to external resources.
Twitter URL Update:

Replaced the outdated Twitter URL (https://twitter.com/) with the updated x.com format (https://x.com/) to align with the platform's rebranding.

Author: sergeypanin1994

CONTRIBUTION.md

@@ -9,7 +9,7 @@ Welcome to the web3.unity project! We appreciate your interest in contributing t
 
 ### Forking the Repository
 
-If you're unfamiliar with Forking, here is a quick guide on how to fork our repo:
+If you're unfamiliar with Forking, here is a quick guide on how to fork our repository:
 
 1. Go to the [web3.unity repository](https://github.com/ChainSafe/web3.unity) on GitHub.
 2. Click the "Fork" button in the top-right corner of the page.
@@ -18,6 +18,7 @@ If you're unfamiliar with Forking, here is a quick guide on how to fork our repo
 ## Setting Up the Development Environment
 
 ### macOS
+
 **Note: If you're building the project for iOS, you have to install Xcode.**
 
 1. **Install Unity**: Install Unity Hub by downloading it from Unity's official website.
@@ -61,7 +62,9 @@ UnitySampleProject also contains a lot of different packages that are dependent
 Because we have two projects, developers can often be confused about in which project they should start writing the code. 
 General rule of thumb:
 1. If your code will directly use some of the Unity features, it should probably live inside the UnitySampleProject. 
-Note: If you want to add a new module (like web3auth, ramp, or lootboxes), you should create a new package inside the Root of the repository's Packages folder.
+
+Note: If you want to add a new module (like web3auth, ramp, or lootboxes), create a new package in the root of the repository's Packages folder.
+
 2. If your code doesn't care much about Unity but is doing a lot of communication with the blockchain itself, you should definitely create a new csproj inside our Chainsafe.Gaming solution. 
 
 If you're unsure how you would actually extend Chainsafe's SDK, take a look at this lengthy [video](https://youtu.be/D6_786zPva8). It shows in depth how you can add your own code and injectors to the Chainsafe.Gaming project.

Modules.md

@@ -48,7 +48,8 @@ but don't let that stop you from creating your own project for a new module.
 # Dependency injection
 
 Later when user requests `web3.Provider`, DI framework handles this requests and creates an 
-instance of `JsonRpcProvider` with all it's dependencies injected using its constructor.
+
+instance of `JsonRpcProvider` with all its dependencies injected using its constructor.
 
 ```csharp
 public JsonRpcProvider(JsonRpcProviderConfiguration configuration,
@@ -66,7 +67,8 @@ as dependencies.
 
 # Component configuration
 
-`JsonRpcProviderConfiguration` is a simple data object used to configure `JsonRpcProvider`. It look like this:
+`JsonRpcProviderConfiguration` is a simple data object used to configure `JsonRpcProvider`. it looks like this:
+
 ```csharp
 [Serializable]
 public class JsonRpcProviderConfiguration
@@ -109,7 +111,8 @@ public Web3Builder()
     _serviceCollection.AddSingleton<ChainProvider>();
 }
 ```
-If you ever need to bind a service, that's' not swappable and can be used by many other components 
+
+If you ever need to bind a service, that's not swappable and can be used by many other components 
 as some sort of helper, bind it here. No interface required this time.
 
 If your service is platform dependent you'd have to bind it as an Environment service.
@@ -166,12 +169,14 @@ But for now there are 3 classes:
 * `ProviderMigration`
 * `SignerMigration`
 
+
 Most of code is compatible by default, but for Provider and Singer we have to use 
 this for object instantiation:
 ```csharp
 var provider = ProviderMigration.NewJsonRpcProvider("http://127.0.0.1:7545");
 var signer = SignerMigration.NewJsonRpcSigner(provider);
 ```
+
 _Migration might not be the best word for describing this process. Ping me (@oleksandrchainsafe) if you have better ideas._
 
 # Useful links

README.md

@@ -2,6 +2,7 @@
 
 
 [<img alt="Discord" src="https://img.shields.io/discord/593655374469660673.svg?style=for-the-badge&label=Discord&logo=discord" height="20">](https://discord.gg/Q6A3YA2)
+
 [<img alt="Twitter" src="https://img.shields.io/twitter/follow/chainsafeth" height="20">](https://x.com/chainsafeth)
 
 ## Documentation