adding some new repos

docs/fud-faq.md

@@ -68,7 +68,9 @@ We urge the Ergo community—both miners and developers—to actively participat
 
 ### Ergo's marketing sucks.
 
-Ergo's marketing strategy is community-driven and organic, focusing on building a strong, knowledgeable, and engaged community. While it may not follow the traditional marketing strategies seen in other projects, this approach ensures that the community is well-informed and actively involved in the project's development. Ergo's unique features and capabilities are its main selling points, and the team believes in letting these aspects speak for themselves. The project also regularly communicates updates and developments through various channels, including social media, blog posts, and community meetings.
+Ergo's marketing strategy is rooted in community engagement and organic growth, diverging from conventional marketing tactics often employed by other projects. This strategy prioritizes the cultivation of a well-informed and actively involved community. Ergo's unique features and capabilities serve as its primary selling points, and the team is committed to letting these attributes stand out on their own. Regular updates and developments are communicated through various channels, including social media, blog posts, and community meetings.
+
+The marketing efforts are primarily aimed at increasing awareness, educating the community, and highlighting the unique features and capabilities of Ergo. The objective is to stimulate organic growth and attract users who value the platform's technological advantages and commitment to privacy, security, and genuine decentralization. The [Sigmanauts](sigmanauts.md) programme has been successful, with mature pathways that allow for a smooth transition for individuals to make meaningful contributions and help shape and grow Ergo. This resilient marketing approach was designed to kickstart truly organic and decentralized compounding growth. Now, with their own treasury, the Sigmanauts are making proposals and expenditures, running campaigns, creating content, attending events, and planning for the future.
 
 ### Ergo won't succeed without VC investment
 

docs/node/install/manual.md

@@ -4,7 +4,7 @@ This document provides a systematic process for the manual installation of an Er
 
 ---
 
-The node uses Java so should work across all operating systems. You can even run on a [Raspberri Pi](pi.md). The only hardware requirement is ~20GB of space to store the chain and ~8GB of RAM for handling the sync.
+The node uses Java so should work across all operating systems. You can even run on a [Raspberry Pi](pi.md). The only hardware requirement is ~20GB of space to store the chain and ~8GB of RAM for handling the sync.
 
 
 

docs/node/install/pi.md

@@ -4,11 +4,13 @@
 
 The Raspberry Pi is small, inexpensive, and meets the requirements to run an Ergo full node.
 
+Alternatively to the simple instructions below, see [Tutorial: Running an Ergo Full Node on a Headless Raspberry Pi](https://github.com/ccgarant/ergo-full-node-raspi) for a more comprehensive start to finish setup guide. 
+
 
 ### Prerequisites 
 
 - Pi4 with 4gb RAM or above is optimal. 
-- Due to the intensive disk I/O, a SSD with 64GB+ is preferred. 
+- Due to the intensive disk I/O, a SSD with 64GB+ is preferred.
 
 ### Preperation
 

docs/uses/oracles.md

@@ -11,7 +11,7 @@ External oracle data, when posted on-chain, must be precisely encoded within a t
 
 ### Introduction to Oracle Pools V2
 
-The following section delves into the Oracle Pools V2, an innovative upgrade to the existing oracle pool v1.0, as documented in [EIP16](https://github.com/ergoplatform/eips/blob/eip16/eip-0016.md). This proposed update is designed to resolve various drawbacks associated with the first version such as generation of extensive dust, low rewards, complexity due to two types of pool boxes, and issues related to the non-transferability of oracle and ballot tokens.
+The following section delves into the Oracle Pools V2, an innovative upgrade to the existing Oracle Pool v1.0, as documented in [EIP16](https://github.com/ergoplatform/eips/blob/eip16/eip-0016.md). This proposed update is designed to resolve various drawbacks associated with the first version such as the generation of extensive dust, low rewards, complexity due to two types of pool boxes, and issues related to the non-transferability of oracle and ballot tokens.
 
 Oracle Pools V2 offers a range of new features and improvements including a single pool address, an epoch counter, a compact pool box, a refresh box, token-based rewards, no separate funding process, reward accumulation, and transferability of oracle and ballot tokens.
 
@@ -21,7 +21,7 @@ To gain a deeper understanding of these changes and how they enhance the overall
 
 For further details, refer to [Oracles-V2](oracles-v2.md).
 
-
+For an easy docker setup see [easy-ergo-oracle](https://github.com/reqlez/ergo-easy-oracle)
 
 ## Resources