update content (#38)

about/architect.md

@@ -13,7 +13,7 @@ Waku was built as open-source public goods infrastructure to serve as the commun
 
 - **Runs anywhere:** Waku was designed to run in resource-restricted environments—like phones and browsers—enabling users operating lower-spec hardware or with intermittent bandwidth to participate as peers.
 
-- **Privacy first:** Waku empowers developers to build apps that cannot harvest users' metadata, removing the need for users to trust that their data is not used maliciously or without their consent.
+- **Privacy first:** Waku empowers developers to build apps that cannot harvest users' metadata, removing the need for them to trust that their data is not used maliciously or without their consent.
 
 - **Modular:** Waku's modularity enables developers to make tradeoffs according to their users' privacy expectations and performance demands by implementing only those protocols that are relevant to their applications. While one app might value privacy above all else, another may be willing to make compromises to deliver a more frictionless UX.
 
@@ -26,7 +26,9 @@ Waku was built as open-source public goods infrastructure to serve as the commun
 The Waku team has developed three clients to run in different environments along with a range of SDKs in Rust, React Native, Kotlin and Swift:
 
 - nwaku: Waku's reference implementation written in Nim.
+
 - go-waku: An implementation for native integration with Golang applications.
+
 - js-waku: Waku's JavaScript implementation for browser environments.
 
 Waku is best thought of as a cohesive whole in terms of its capabilities. However, under the hood are three distinct network interaction domains: gossip, discovery and request/response.
@@ -35,7 +37,7 @@ Waku is best thought of as a cohesive whole in terms of its capabilities. Howeve
 
 Waku compromises multiple protocols, including but not limited to the following:
 
-**Waku Relay**: The heart of Waku v2, the relay protocol specifies a pub/sub approach to p2p messaging with a focus on privacy, censorship resistance and security, and is currently implemented as a minor extension of the libp2p GossipSub protocol.
+**Waku Relay**: The heart of Waku v2, the relay protocol specifies a pub/sub approach to P2P messaging with a focus on privacy, censorship resistance and security, and is currently implemented as a minor extension of the libp2p GossipSub protocol.
 
 **Waku Filter**: A lighter-weight version of the relay protocol for resource-restricted devices, Waku Filter enables light nodes to only receive the messages they want from full nodes.
 
@@ -43,10 +45,11 @@ Waku compromises multiple protocols, including but not limited to the following:
 
 **Waku Light Push**: A request/response protocol that enables nodes with short connection windows or limited bandwidth to publish messages to the Waku network
 
+
 <br/>
 
 ![architect](/subpages/architect.png)
 
 <br/>
 
-[Dive into the docs](https://vac.dev/research)
+[Dive into the docs](https://docs.waku.org)

about/index.md

@@ -5,17 +5,23 @@ sidebar_position: 1
 
 Waku is the communication standard for the decentralized web. A suite of generalized messaging protocols, it enables private, secure, bidirectional human-to-human, machine-to-machine and human-to-machine communication without reliance on centralized intermediaries.
 
+Waku serves as the communications branch of the [Logos](https://logos.co/) tech stack. Alongside the computational branch, [Nomos](http://www.nomos.tech), and the storage branch, [Codex](http://www.codex.storage), it is one of the Logos Collective's foundational projects. 
+
+<br/>
+
+### Motive
+
 Today's internet is increasingly controlled by a vanishingly small number of tech giants. The Googles, Amazons and Metas of the world dictate what we see and with whom we can communicate. Their influence is absolute, and their actions shape global public opinion and even geopolitics. 
 
 To anyone that understands the internet's present architecture, this outcome should be expected. The centralized entities through which we communicate have privileged access to reams of data that we, as internet users, produce daily, presenting an opportunity for the kind of surveillance that was once confined to the pages of science-fiction literature. Thinking that the most powerful commercial and political institutions would not leverage this would be naive. 
 
-Yet, it doesn't have to be this way. Advances in cryptography, p2p technologies and decentralized networking provide an alternate path forward.
+Yet, it doesn't have to be this way. Advances in cryptography, P2P technologies and decentralized networking provide an alternate path forward.
 
 <br/>
 
-## (Slowly) moving toward a decentralized web
+### (Slowly) moving toward a decentralized web
 
-The early Ethereum community realized this. Initially, the plan was to rebuild the web's architecture along decentralized lines by developing the so-called "Holy Trinity of the Decentralized Web." Ethereum itself would handle logic, Swarm was the reimagined web's storage layer and Whisper would take care of messaging.
+The early Ethereum community realized this. Initially, the plan was to rebuild the web's architecture along decentralized lines by developing the so-called "Holy Trinity of the Decentralized Web." Ethereum itself would handle computation, Swarm was the reimagined web's storage layer and Whisper would take care of messaging. 
 
 <br/>
 
@@ -25,12 +31,15 @@ The early Ethereum community realized this. Initially, the plan was to rebuild t
 
 Whisper was a promising start but scalability shortcomings quickly became apparent. Meanwhile, for reasons upon which we can only speculate, the development of Swarm and Whisper was relegated to a backseat while Ethereum took center stage. Yet, without adequate communication and storage layers, the decentralized web's potential for disruption remained severely handicapped.
 
-Status, the decentralized messaging application, hoped to leverage Whisper but with development grinding to a snail's pace, it was forced to take up the job itself. Consequently, the R&D group Vac was put together in 2018 to research solutions to Whisper's scaling woes.
+Status, the decentralized messaging application, hoped to leverage Whisper but with development grinding to a snail's pace, it was forced to take up the job itself. Consequently, the R&D group [Vac](https://vac.dev/) was put together in 2018 to research solutions to Whisper's scaling woes.
+
 
 <br/>
 
-## The birth of Waku
+### The birth of Waku
 
 In 2020, Waku v1 was released. A fork of the Whisper codebase, this initial version introduced various Vac-proposed optimizations, resulting in a more performant messaging protocol. Yet, it was clear that further changes were needed if Waku was to handle the volume of messages an application like Status would produce.  
 
 The following year, work on a complete protocol rewrite began. Waku v2, as the version under development today is known, introduced a relay protocol that implements pub/sub over libp2p. Additionally, further capabilities were included to make Waku more useful, including historic message retrieval for often-offline devices, adaptive nodes to make participation more accessible to users with limited or intermittent connections and lower-spec hardware, and various bandwidth preservation techniques.   
+
+Waku was first announced as a core Logos project in June 2023.    

about/roadmap.md

@@ -7,7 +7,7 @@ Waku v1 is in production and was quickly adopted by the Status Mobile applicatio
 
 Given Waku v1's scaling difficulties, the team behind Waku is primarily focused on ensuring v2 scales securely. By the end of Q2 2023, we aim to support more than one million users. 
 
-Meanwhile, the team is also working on ensuring production readiness alongside network and development sustainability. Although work on these areas is already underway, our efforts will intensify as we make progress toward our million-user-milestone. Finally, Waku aims to promote itself among developers looking to add decentralized communications to their applications.
+Meanwhile, the team is also working on ensuring production readiness alongside network and development sustainability. Although work on these areas is already underway, our efforts will intensify as we progress toward our million-user-milestone. Finally, Waku aims to promote itself among developers looking to add decentralized communications to their applications.
 
 <br/>
 
@@ -31,7 +31,10 @@ We believe Waku will only realize its true potential if its community and users
 
 ## Growth
 
-After achieving the above milestones, we will be in a position to aggressively market Waku to potential contributors and developers within the web3 sector and beyond. As a piece of public goods infrastructure, we encourage the wider community to help improve the protocols by contributing to our R&D efforts. However, promotion is an ongoing process that is already underway, involving conference attendance and sponsorship, hosting developer workshops, producing promotional material, and appearing on industry-focused podcasts.
+After achieving the above milestones, we will be in a position to aggressively market Waku to potential contributors and developers within the web3 sector and beyond. As a piece of public goods infrastructure, we encourage the wider community to help improve the protocols by contributing to our R&D efforts. 
+
+Promotion is an ongoing process that is already underway, involving conference attendance and sponsorship, hosting developer workshops, producing promotional material, and appearing on industry-focused podcasts.
+
 
 <br/>
 
@@ -41,4 +44,5 @@ Completing the roadmap objectives described above will best position Waku for ma
 
 Similarly, it makes little sense to promote Waku aggressively until we are confident that it can handle waves of new users without degraded performance. Without first achieving secure scalability and proving production readiness, it will be very difficult to convince all but the most ideologically driven developers to continue believing in Waku's potential if their first experience is a negative one. 
 
+
 [Contribute to Waku](https://github.com/waku-org)

about/team.md

@@ -3,7 +3,7 @@ title: Core contributors
 sidebar_position: 3
 ---
 
-Leading Waku's R&D efforts is Franck Royer. Royer draws on more than five years of experience within the blockchain and crypto ecosystem, and over 13 years as a software engineer and team lead with a primary focus on backend development for mission-critical applications.
+Leading Waku's R&D efforts is Franck Royer. Franck draws on more than five years of experience within the blockchain and crypto ecosystem, and over 13 years as a software engineer and team lead with a primary focus on backend development for mission-critical applications.
 
 The core contributors building Waku are split into three subgroups: 
 
@@ -15,7 +15,7 @@ Our research efforts are led by a former telecoms engineer with almost a decade
 
 Waku's development arm is broken down by client implementation. 
 
-- nwaku: The team building nwaku, our implementation in Nim, comprises two software engineers with more than two decades of combined experience within the fields of backend development, open-source development, artificial intelligence and finance.
+- nwaku: The team building nwaku, our implementation in Nim, comprises two software engineers with more than two decades of combined experience in backend development, open-source development, artificial intelligence and finance.
 
 - js-waku: Our JavaScript implementation is developed by a senior and intermediate software engineer, one with extensive experience in the web3 sector and another who previously worked with renowned tech companies, such as Microsoft and Ubisoft.
 

src/pages/index.mdx

@@ -135,7 +135,7 @@ import {
     title="Development roadmap"
     description="Waku has the ambitious goal of attracting and supporting millions of simultaneous users, truly serving as the communications standard across web3. Our development roadmap focuses on achieving secure scalability before implementing incentivization mechanisms to sustain Waku."
     label="Read more"
-    href="/about/development-roadmap"
+    href="/about/roadmap"
   />
 </Box>