Patch 1

docs/index.md

@@ -15,7 +15,7 @@ hide_sidebar: true
 
 # Welcome to Qubic Documentation
 
-Qubic is an innovative platform designed to revolutionize the world of decentralized computing and finance through its quorum-based computer (QBC) system. Whether you're a developer, researcher, or enthusiast, this documentation will guide you through everything you need to know to start building and contributing to the Qubic ecosystem.
+Qubic is an innovative platform designed to revolutionise the world of decentralised computing and finance through its quorum-based computer (QBC) system. Whether you're a developer, researcher, or enthusiast, this documentation will guide you through everything you need to know to start building and contributing to the Qubic ecosystem.
 
 ## Getting Started
 
@@ -24,25 +24,24 @@ Ready to dive in? Start here to learn the basics and set up your environment:
 - [Introduction to Qubic](overview/introduction.md): Get a high-level overview of what Qubic is and how it works.
 
 - [Create your Qubic Wallet](learn/invest.md): Learn about the various ways to invest in Qubic, including cryptocurrency exchanges and creating a Qubic wallet.
+
 ## Learn
 
 Expand your knowledge of the Qubic platform:
 
 - [Tokenomics](learn/tokenomics.md): Understand the economic model and utility of Qubic Units (QUs) in the ecosystem.
 
-- [Useful Proof of Work (uPoW)](learn/upow.md): Discover how uPoW underpins the security and efficiency of the system.
+- [Useful Proof of Work (UPoW)](learn/UPoW.md): Discover how uPoW underpins the security and efficiency of the system.
 
 - [Quorum](learn/quorum.md): Explore how Qubic's quorum-based computer system operates.
 
-- [Aigarth](learn/aigarth.md): Learn about Aigarth project being developed on the Qubic network.
+- [Aigarth](learn/aigarth.md): Learn about Aigarth being developed on the Qubic network.
 
 ## Developer Resources
 
 Everything you need to start developing on Qubic:
 
 ## Tutorials
-
-
 - [Tutorials](developers/tutorials.md): Comprehensive guides and examples to help you get started with Qubic development.
 
 ## Clients

docs/learn/aigarth.md

@@ -4,7 +4,7 @@ sidebar_label: 'Aigarth'
 
 # Aigarth - The AI Garden on Qubic Network
 
-Aigarth is a pioneering project that will be developed on top of the Qubic network. It combines the fields of artificial intelligence and distributed computing to create a collective system for solving complex AI tasks. The name "Aigarth" is a fusion of "AI" for artificial intelligence, and "garth," an old term for garden or yard.
+Aigarth is a pioneering project that is being developed on top of the Qubic network. It combines the fields of artificial intelligence and distributed computing to create a collective system for solving complex AI tasks. The name "Aigarth" is a fusion of "AI" for artificial intelligence, and "garth," an old term for garden or yard.
 
 :::note
 
@@ -31,4 +31,4 @@ The fundamental block of Aigarth's special algorithm is the Helix logic gate. Th
 
 ## What's on the Horizon?
 
-Aigarth is dependent on Qubic, and the development milestones will be more explicit once Qubic is running. With its unique approach to solving AI problems, Aigarth represents a fascinating combination of distributed computing and artificial intelligence.
+With its unique approach to solving AI problems, Aigarth represents a fascinating combination of distributed computing and artificial intelligence.

docs/learn/arbitrator.md

@@ -1,2 +1,2 @@
 # Arbitrator
-An entity within the Qubic ecosystem responsible for resolving disputes and protecting user interests. The arbitrator sets parameters of the mining algorithm, publishes lists of computors every epoch, is developing the capacity to replace faulty computors, and accumulates QUs not received by underperforming computors. Each node operator individually selects their arbitrator by setting the corresponding ID in Qubic.cpp. The entity controlling the current arbitrator remains unknown, though rumors suggest it's operated by the development team.
+An entity within the Qubic ecosystem responsible for resolving disputes and protecting user interests. The Arbitrator sets the parameters of the mining algorithm, publishes lists of Computors every epoch, and has the capacity to replace underperforming Computors. The Arbitrator receives the remaining revenue, which is about 1% per epoch, after Computors have been allocated their share. Each Computor individually selects their Arbitrator by setting the corresponding ID in Qubic.cpp. The entity controlling the current Arbitrator remains unknown, though rumours suggest it is operated by the development team. Computors have the ability to collectively override or replace the Arbitrator through a consensus process. This feature is crucial in preventing any single entity from gaining excessive control over the network.

docs/learn/decision-making.md

@@ -1,7 +1,6 @@
 # Decision Making (Draft)
 
-Qubic operates on a democratic model. Every member of the community has a say in decision making. Community input is essential to maintaining the decentralized nature of Qubic and ensuring its evolution aligns with the needs and wants of its users, with key decisions made collectively by the [Quorum](/learn/quorum). This process ensures that all voices are heard and that the ecosystem evolves in a way that benefits all users.
-
+Qubic operates on a democratic model. Every member of the community has a say in decision making. Community input is essential to maintaining the decentralised nature of Qubic and ensuring its evolution aligns with the needs and wants of its users, with key decisions made collectively by the [Quorum](/learn/quorum). This process ensures that all voices are heard and that the ecosystem evolves in a way that benefits all users.
 
 ## How Decisions are Made
 
@@ -10,16 +9,13 @@ Decision-making in Qubic involves several steps:
 1. **Idea:** Any member of the Qubic community can propose a change or new feature. This idea is then shared with the entire community for consideration.
 2. **Discussion:** Community members can discuss the idea, ask questions, and offer feedback. The person who made the proposal may revise it based on the feedback received.
 3. **Proposal:** After a thorough discussion, the idea can evolve into a formal proposal. This proposal incorporates all the feedback and revisions from the community discussion. It provides a detailed plan of action, clearly stating what the change or new feature is and how it will be implemented.
-4. **Voting:** Once the proposal is finalized, it is put to a vote. A quorum must participate in the vote for the decision to be valid. The specific number constituting a quorum may vary depending on the significance of the decision.
-5. **Implementation:** If the proposal receives majority support in the vote, it is accepted and moves into the implementation phase. If not, it is either revised for further consideration or discarded.
+4. **Voting:** Once the proposal is finalised, it is put to a vote. The Quorum must participate in the vote for the decision to be valid. 
+5. **Implementation:** If the proposal receives majority support in the Computor vote, it is accepted and moves onto the implementation phase. If not, it is either revised for further consideration or discarded.
 
 ## Why is the Quorum important?
 
-The quorum ensures that decisions are not made by a small subset of the community. By requiring a minimum level of participation, the quorum ensures that a wide cross-section of the community is represented in each decision.
-
-The quorum-based decision-making process in Qubic promotes fairness, transparency, and inclusivity. It gives every computor a say in the project's future and helps to build a more robust and resilient Qubic ecosystem.
-
+The quorum-based decision-making process in Qubic promotes fairness, transparency, and inclusivity. It gives every Computor a say in the project's future and helps to build a more robust and resilient Qubic ecosystem.
 
 ## Your Role in Decision Making
 
-As a member of the Qubic community, you have a role to play in decision making. You're encouraged to submit ideas, review and comment on existing ideas, draft proposals and participate in the voting process (if you have the state of a computor). Your voice matters, so don't hesitate to get involved and help shape the future of Qubic!
+As a member of the Qubic community, you have a role to play in decision making. You are encouraged to submit ideas, review and comment on existing ideas, draft proposals and participate in the voting process (if you have the status of a Computor). Your voice matters, so do not hesitate to get involved and help shape the future of Qubic!

docs/learn/dispute-resolution.md

@@ -1,10 +1,10 @@
 # Dispute Resolution (Draft)
 
-Disputes are inevitable in any community, and Qubic is no exception. However, Qubic employs an effective dispute resolution process to ensure that disagreements are handled in a fair, transparent, and amicable manner. This approach involves several steps and emphasizes community participation and consensus.
+Disputes are inevitable in any community, and Qubic is no exception. However, Qubic employs an effective dispute resolution process to ensure that disagreements are handled in a fair, transparent, and amicable manner. This approach involves several steps and emphasises community participation and consensus.
 
 ## The Arbitrator
 
-An integral component of Qubic's dispute resolution process is the [Arbitrator](/learn/arbitrator). The Arbitrator is responsible for resolving disagreements and protecting users' interests within the Qubic ecosystem. Its key duties include setting parameters of the mining algorithm, publishing computor lists every epoch, replacing faulty computors, and accumulating Qus not received by poorly performing computors.
+An integral component of Qubic's dispute resolution process is the [Arbitrator](/learn/arbitrator). The Arbitrator is responsible for resolving disagreements and protecting users' interests within the Qubic ecosystem. Its key duties include setting parameters of the mining algorithm, publishing computor lists every epoch, replacing faulty computors, and accumulating QUBIC not received by poorly performing computors.
 
 ## How Does Dispute Resolution Work?
 

docs/learn/glossary.md

@@ -10,7 +10,7 @@ The following terms are used throughout the Qubic documentation and development
 Aigarth is an AI-oriented project that will run on the Qubic network, which aims to utilize unused computational power for solving AI-related tasks. Its primary function is to run a special algorithm that allows for the evolution of solutions based on Helix logic gates. This process is transparent, with progress points available to all participants, promoting a collective push towards efficient solutions.
 
 ## Arbitrator
-An entity within the Qubic ecosystem responsible for resolving disputes and protecting user interests. The [Arbitrator](/learn/arbitrator) sets parameters of the mining algorithm, publishes lists of computors every epoch, is developing the capacity to replace faulty computors, and accumulates QUs not received by underperforming computors. Each node operator individually selects their arbitrator by setting the corresponding ID in Qubic.cpp. The entity controlling the current arbitrator remains unknown, though rumors suggest it's operated by the development team.
+An entity within the Qubic ecosystem responsible for resolving disputes and protecting user interests. The [Arbitrator](/learn/arbitrator) sets parameters of the mining algorithm, publishes lists of computors every epoch, is developing the capacity to replace faulty computors, and accumulates QUBIC not received by underperforming computors. Each node operator individually selects their arbitrator by setting the corresponding ID in Qubic.cpp. The entity controlling the current arbitrator remains unknown, though rumors suggest it's operated by the development team.
 
 ## Candidate
 A Candidate is a node that runs the [Computors](/learn/nodes) software but hasn't yet achieved the status of a Computor. In each epoch, up to 256 candidates can ascend to Computor status if they rank among the top 676 nodes based on their score. It's important to note that only Computors with a full week's status receive Qubic Units (QUs) as rewards for their performance. While Candidates don't earn any QUs, running as a Candidate is essential for pushing solutions to the blockchain, which is a prerequisite for becoming a Computor.
@@ -37,7 +37,7 @@ Miners in Qubic are essential for supporting Computors. Miners acquire problems
 A feature in development for Qubic. In blockchain technology, oracles are third-party services that provide smart contracts with external information, enabling them to interact with the outside world.
 
 ## QU
-QUs or [Qubic Units](/learn/tokenomics) is the native coin and positioned as equivalent of "energy" units spent to run smart-contract and access other services in Qubic (e.g. donations to oracles). Yes, QUs can be used as money, but they are more than that. Transfers are feeless and notion of "fee" for smart contracts doesn't make much sense, because qus are destroyed, not given to computors. When one asks an oracle he "burns" QUs as a sacrifice, not as a payment, it's not even guaranteed that the oracle will answer. 
+QUs or QUBIC [Qubic Units](/learn/tokenomics) is the native coin and positioned as equivalent of "energy" units spent to run smart contracts and access other services in Qubic (e.g. donations to oracles). Yes, QUs can be used as money, but they are more than that. Transfers are feeless and notion of "fee" for smart contracts doesn't make much sense, because qus are destroyed, not given to computors. When one asks an oracle he "burns" QUs as a sacrifice, not as a payment, it's not even guaranteed that the oracle will answer. 
 
 ## Quorum
 A quorum is the minimum number of computors necessary to conduct any sort of business. In Qubic the [Quorum](/learn/quorum) is ⅔ (or 451) of all Computors to reach consensus.
@@ -46,7 +46,7 @@ A quorum is the minimum number of computors necessary to conduct any sort of bus
 Self-executing contracts with the terms of the agreement directly written into code. Qubic's first [smart contract](/learn/smart-contracts) was an Initial Public Offering ([IPO](/learn/ipo)) of 676 shares for a decentralized exchange (DEX) named [Qx](/learn/qx).
 
 ## Spectrum
-Qubic's equivalent of a ledger. In the [Spectrum](/learn/spectrum) the energy (i.e. QUs) per Identity is stored. Qubic itself doesn not keep track of transactions.
+Qubic's equivalent of a ledger. In the [Spectrum](/learn/spectrum) the energy (i.e. QUs) per Identity is stored. Qubic itself does not not keep track of transactions.
 
 ## Ticks
 In the Qubic ecosystem, the tick is the interval within which the Quorum commes to an agreement on transactions and the outcome computed smart contracts. A single tick can last a very short interval of time (below 1 second).
@@ -57,4 +57,4 @@ A novel consensus mechanism that optimizes the energy expended in mining process
 
 \_
 
-Please note that Qubic is still in development, and some aspects of the system are subject to change during the development and practical testing phase. No official whitepaper is available as of yet due to this ongoing development process.
+Please note that Qubic is still in development, and some aspects of the system are subject to change during the development and practical testing phase. No official whitepaper is available as of yet due to this ongoing development process.

docs/learn/governance.md

@@ -3,10 +3,10 @@ sidebar_label: 'Separation of Power'
 ---
 
 # Separation of Power
-The Qubic system has been designed with the core principle of decentralization in mind. The unique approach to governance ensures that power within the system is not concentrated in a single entity. This is achieved through the separation of power between the [Quorum](/learn/quorum) and the [Arbitrator](/learn/arbitrator).
+The Qubic system has been designed with the core principle of decentralisation in mind. The unique approach to governance ensures that power within the system is not concentrated in a single entity. This is achieved through the separation of power between the [Quorum](/learn/quorum) and the [Arbitrator](/learn/arbitrator).
 
-The Quorum is defined as a group of ⅔+ (or 451+) [Computors](/learn/nodes) that participate in making important network decisions such as validating transactions and maintaining consensus (i.e reaching the same result before considering it final). The Arbitrator, on the other hand, resolves disagreements, sets parameters for the mining algorithm, publishes Computor lists after each epoch and accumulates qus from underperforming Computors.
+The Quorum is defined as a group of ⅔+ (or 451+) [Computors](/learn/nodes) that participate in making important network decisions such as validating transactions and maintaining consensus (i.e reaching the same result before considering it final). The Arbitrator, on the other hand, resolves disagreements, sets parameters for the mining algorithm, publishes Computor lists after each epoch, and can remove underperforming Computors. To ensure there is no incentive to collude, the Arbitrator receives the remaining revenue after Computors have been allocated their reward. This averages around 1% per epoch.
 
-Both entities play significant roles in the Qubic ecosystem. However, it is crucial to prevent one entity from controlling both the Quorum and the Arbitrator to preserve the integrity and decentralization of the network. If the same entity controls both, it may create an environment where Computors could choose to maintain their own status instead of promoting a healthy competition. This could potentially disrupt the overall balance of the network and hinder its growth and development.
+Both entities play significant roles in the Qubic ecosystem. However, it is crucial to prevent one entity from controlling both the Quorum and the Arbitrator to preserve the integrity and decentralisation of the network. If the same entity controls both, it may create an environment where Computors could choose to maintain their own status instead of promoting a healthy competition. This could potentially disrupt the overall balance of the network and hinder its growth and development.
 
-In conclusion, the separation of power in Qubic is not just about distributing responsibilities; it's about preserving the core principle of decentralization and ensuring the network remains robust, fair, and democratic.
+In conclusion, the separation of power in the Qubic ecosystem is not just about distributing responsibilities; it's about preserving the core principle of decentralisation and ensuring the network remains robust, fair, and democratic.