Corrected typos

README.md

@@ -33,7 +33,7 @@ Key features of the Masa network include:
 
 Masa empowers contributors to monetize their data and compute resources by becoming Worker Nodes on the network. As a Worker Node, you can:
 
-- Stake tokens to provide work to the network and earn rewards for your nodes availablity and uptime.
+- Stake tokens to provide work to the network and earn rewards for your nodes availability and uptime.
 - Receive and process data requests from Oracle Nodes, servicing data and LLM requests.
 - Earn network emissions and fees for the work you provide, generating a new revenue stream.
 - Access the network's vast dataset and LLM resources to efficiently process requests and deliver accurate results.

RELEASE_NOTES.md

@@ -10,7 +10,7 @@ This release of the Masa Oracle Node introduces the following new features and c
 
 ### Breaking Changes
 
-* Protocol verion change to 0.5.0
+* Protocol version change to 0.5.0
 
 ### Bug fixes
 

cmd/masa-node/main.go

@@ -30,7 +30,7 @@ func main() {
 	}
 
 	if len(os.Args) > 1 && os.Args[1] == "--version" {
-		logrus.Infof("Masa Oracle Node Version: %s\nMasa Oracle Protocol verison: %s", versioning.ApplicationVersion, versioning.ProtocolVersion)
+		logrus.Infof("Masa Oracle Node Version: %s\nMasa Oracle Protocol version: %s", versioning.ApplicationVersion, versioning.ProtocolVersion)
 		os.Exit(0)
 	}
 

docs/oracle-node/twitter-data.md

@@ -5,11 +5,11 @@ title: Twitter Data
 
 ## Introduction
 
-This gide serves as a comprehensive guide to utilizing the Twitter data endpoints available through the Masa Oracle Node API. It is designed to assist developers in harnessing the power of real-time Twitter data for a variety of applications, from sentiment analysis, to trend monitoring, and model fine-tuning. Before diving into the technical details, it's important to ensure that your Masa Oracle Node is properly staked. If you want to contribute to the network as a worker please add necessary Twitter credentials so your node can fullfill requests. This guide will walk you through the prerequisites, provide detailed information on how to access and use the Twitter endpoints, and offer example use case of deploying a decentralized AI agent for social media analysis. Whether you're looking to analyze public sentiment, track trending topics, or gather data for your AI Agents, this guide will equip you with the knowledge to effectively integrate Twitter data into your project.
+This gide serves as a comprehensive guide to utilizing the Twitter data endpoints available through the Masa Oracle Node API. It is designed to assist developers in harnessing the power of real-time Twitter data for a variety of applications, from sentiment analysis, to trend monitoring, and model fine-tuning. Before diving into the technical details, it's important to ensure that your Masa Oracle Node is properly staked. If you want to contribute to the network as a worker please add necessary Twitter credentials so your node can fulfill, fulfil requests. This guide will walk you through the prerequisites, provide detailed information on how to access and use the Twitter endpoints, and offer example use case of deploying a decentralized AI agent for social media analysis. Whether you're looking to analyze public sentiment, track trending topics, or gather data for your AI Agents, this guide will equip you with the knowledge to effectively integrate Twitter data into your project.
 
 ## How It Works: Processing Twitter Data Requests
 
-The Masa Oracle Node employs an actor-based model to efficiently process Twitter data requests, enabling real-time access to Twitter data that is sourced through a decentralized network of workers. Each worker is able to fullfill a request and provide data to the network. This section outlines the workflow from receiving a request to delivering data back to the API.
+The Masa Oracle Node employs an actor-based model to efficiently process Twitter data requests, enabling real-time access to Twitter data that is sourced through a decentralized network of workers. Each worker is able to fulfill, fulfil a request and provide data to the network. This section outlines the workflow from receiving a request to delivering data back to the API.
 
 ### Step 1: Initialization
 

docs/welcome-to-masa/welcome-to-masa.md

@@ -34,7 +34,7 @@ Key features of the Masa network include:
 
 Masa empowers contributors to monetize their data and compute resources by becoming Worker Nodes on the network. As a Worker Node, you can:
 
-- Stake tokens to provide work to the network and earn rewards for your nodes availablity and uptime.
+- Stake tokens to provide work to the network and earn rewards for your nodes availability and uptime.
 - Receive and process data requests from Oracle Nodes, servicing data and LLM requests.
 - Earn network emissions and fees for the work you provide, generating a new revenue stream.
 - Access the network's vast dataset and LLM resources to efficiently process requests and deliver accurate results.

pkg/chain/persistance.go

@@ -9,7 +9,7 @@ const (
 	KeyLastHash = "last_hash"
 )
 
-type Persistance struct {
+type Persistence struct {
 	db *badger.DB
 }
 
@@ -18,7 +18,7 @@ type Serializable interface {
 	Deserialize(data []byte) error
 }
 
-func (p *Persistance) Init(path string, genesisFn func() (Serializable, []byte)) ([]byte, error) {
+func (p *Persistence) Init(path string, genesisFn func() (Serializable, []byte)) ([]byte, error) {
 	dbOptions := badger.DefaultOptions(path)
 	dbOptions.Logger = nil
 	db, err := badger.Open(dbOptions)
@@ -71,7 +71,7 @@ func (p *Persistance) Init(path string, genesisFn func() (Serializable, []byte))
 	return lastHash, nil
 }
 
-func (p *Persistance) Get(key []byte) ([]byte, error) {
+func (p *Persistence) Get(key []byte) ([]byte, error) {
 	var value []byte
 	err := p.db.View(func(transaction *badger.Txn) error {
 		item, err := transaction.Get(key)
@@ -93,11 +93,11 @@ func (p *Persistance) Get(key []byte) ([]byte, error) {
 	return value, nil
 }
 
-func (p *Persistance) GetLastHash() ([]byte, error) {
+func (p *Persistence) GetLastHash() ([]byte, error) {
 	return p.Get([]byte(KeyLastHash))
 }
 
-func (p *Persistance) SaveBlock(hash []byte, block Serializable) error {
+func (p *Persistence) SaveBlock(hash []byte, block Serializable) error {
 	err := p.db.Update(func(transaction *badger.Txn) error {
 		serialData, err := block.Serialize()
 		if err != nil {
@@ -119,7 +119,7 @@ func (p *Persistance) SaveBlock(hash []byte, block Serializable) error {
 	return nil
 }
 
-func (p *Persistance) Iterate(prefix []byte, block Serializable, callback func(value []byte) error) error {
+func (p *Persistence) Iterate(prefix []byte, block Serializable, callback func(value []byte) error) error {
 	err := p.db.View(func(transaction *badger.Txn) error {
 		opts := badger.DefaultIteratorOptions
 		iterator := transaction.NewIterator(opts)

pkg/tests/integration/tracker_test.go

@@ -56,13 +56,13 @@ var _ = Describe("Oracle integration tests", func() {
 			// Wait for the nodes to see each others in their respective
 			// nodeTracker
 			Eventually(func() bool {
-				datas := n2.NodeTracker.GetAllNodeData()
-				return len(datas) == 2
+				data := n2.NodeTracker.GetAllNodeData()
+				return len(data) == 2
 			}, "30s").Should(BeTrue())
 
 			Eventually(func() bool {
-				datas := n.NodeTracker.GetAllNodeData()
-				return len(datas) == 2
+				data := n.NodeTracker.GetAllNodeData()
+				return len(data) == 2
 			}, "30s").Should(BeTrue())
 
 			data := n.NodeTracker.GetAllNodeData()