Skip to content

Commit ec1c85d

Browse files
ehsan6shaclaude
andcommitted
Docs: rewrite remaining present tense and commerce claims
Removes the last statements that described Functionland Inc as an operating project, promised pricing or free service tiers, or spoke in the first person on behalf of an operator: the Functionland project and ecosystem references in the RFC process, troubleshooting and blockchain pages, the pay as you go and competitive pricing copy, the free pinning allowance, the guarantee wording in the introduction, and the contribution pages written as our projects. Also drops the instruction to ask a community member for an invite, and the first person framing of the Indiegogo distribution. Left in place deliberately: the no guarantee disclaimer on uploaded testnet data, which limits rather than promises, the past tense record of the Indiegogo distribution, and the fulatower hostname the device broadcasts. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HSGV9b1NxySBayTu5v2eF4
1 parent cf004ef commit ec1c85d

15 files changed

Lines changed: 23 additions & 23 deletions

File tree

‎docs/RFCs/rfc-process.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,15 +11,15 @@ However, some changes though are "substantial", and we ask that these be put thr
1111
The "RFC" (Request For Comments) process is intended to provide a consistent, controlled path for new features to enter the project, so that all stakeholders and contributors can be confident about the direction the project is evolving in.
1212

1313
## When to follow this process
14-
You should consider using this process if you intend to make "substantial" changes in any Functionland project or the documentation. Here are some examples of things that would benefit from an RFC:
14+
You should consider using this process if you intend to make "substantial" changes in any Fula Network project or the documentation. Here are some examples of things that would benefit from an RFC:
1515
- A new feature that requires rethinking of something that has already been developed and shipped.
1616
- A change in the documentation structure in order to enhance readers experience.
17-
- The introduction of a new idea, concept or convention that is currently not present in Functionland.
17+
- The introduction of a new idea, concept or convention that is currently not present in the Fula Network.
1818

1919
The RFC process will help you attract more attention to your proposal, as well as make sure that everybody gets a chance to participate in shaping and polishing your new idea.
2020

2121
## About the process
22-
In short, to get a major feature added to any of Functionland's projects, you would first get the RFC merged into the RFC repo of that project as a markdown file. At that point the RFC is ‘active’ and may be implemented with the goal of eventual inclusion.
22+
In short, to get a major feature added to any of the Fula Network projects, you would first get the RFC merged into the RFC repo of that project as a markdown file. At that point the RFC is ‘active’ and may be implemented with the goal of eventual inclusion.
2323
* Fork the project repository
2424
* Copy `rfcs/template.md` to `rfcs/0000-my-feature/README.md` (where my-feature is descriptive, don't ask for an RFC number yet)
2525
* Put any accompanying resources (pictures, etc.) in rfcs/0000-my-feature/. You can refer to these in the text.

‎docs/blockchain/blockchain-intro.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,6 @@ And a network explorer is made avaialbe here:
2828
[Network Explorer](https://functionyard.fx.land)
2929

3030
## Simulation
31-
Finally functionlard token simulations are available here:
31+
Finally token simulations are available here:
3232

3333
[Token Simulation](https://machinations.io/community/functionland/new-fula-tokenomics-333bc093169911ee915c02f943517e50)

‎docs/components/WorkInProgress.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,2 @@
11
:::caution WIP Alert
2-
Please note: these instructions remain a work in progress as we continue to evolve, refine and perfect the Fula API. Make sure to check back soon for more details!
2+
Please note: these instructions remain a work in progress as the Fula API evolves. Make sure to check back soon for more details!

‎docs/functionyard/add-storage.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -208,5 +208,5 @@ Ext4 is a linux standard that Windows does not support without some third-party
208208
4. Continue _[Manually Partition and Format for Mac](#macos-terminal)_ instructions, from step 7.
209209

210210
:::info
211-
**Our apps are open-source and built in React Native for cross-platform support. So if you would like to [contribute to the project](https://github.com/functionland/fx-components), that would be greatly appreciated!**
211+
**The apps are open source and built in React Native for cross-platform support. Contributions are welcome at [fx-components](https://github.com/functionland/fx-components).**
212212
:::

‎docs/functionyard/fxblox-app.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -142,7 +142,7 @@ Adding more than one Blox no longer requires logging out and back in. From the w
142142
5. Check them all under the **Blox** tab.
143143

144144
:::info
145-
**Our apps are open source. If you would like to [contribute to the project](https://github.com/functionland/fxblox-web), that would be greatly appreciated!**
145+
**The apps are open source. Contributions are welcome at [fxblox-web](https://github.com/functionland/fxblox-web).**
146146
:::
147147

148148
## Format Drive

‎docs/functionyard/hardware/fxblox-hardware.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ It is important to know which Blox you have. The manual firmware update process
2828
</ol>
2929
</TabItem>
3030
<TabItem value="Plus" label="FxBlox Lite Plus (RK1)">
31-
The FxBlox Lite Plus has a CPU from Rockchip, it is alternatively known as the <b>RK1</b>. About <b>900</b> of these were distributed during our Indiegogo delivery phase. So it is highly likely you have this model. Other than that there are two key ways to tell if you have this model.
31+
The FxBlox Lite Plus has a CPU from Rockchip, it is alternatively known as the <b>RK1</b>. About <b>900</b> of these were distributed during the Indiegogo delivery phase. So it is highly likely you have this model. Other than that there are two key ways to tell if you have this model.
3232
<ol type="1">
3333
<li> <b>Check the barcode.</b> On the side of the original box that the device came in. It should start with <b>`RK1`</b>, like this.
3434
<img src="/img/fxyard-network/nostorage-rk1.jpg" style={{width: 450}}/>

‎docs/functionyard/join-windows.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ id: join-windows
44
---
55
import ReactPlayer from 'react-player';
66

7-
This guide is for getting a Fula node installed on a Windows machine and adding it to testnet. To get an invite, you can ask a community memeber in Telegram or Discord. If already a Blox or NFT owner, you can join testnet with Indiegogo order or wallet address, respectively.
7+
This guide is for getting a Fula node installed on a Windows machine and adding it to testnet. If already a Blox or NFT owner, you can join testnet with Indiegogo order or wallet address, respectively.
88

99
## Video Guide
1010

‎docs/functionyard/troubleshooting/index.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Troubleshooting
22

3-
This section contains solutions to common issues you might encounter while using FxBlox and the Functionland ecosystem.
3+
This section contains solutions to common issues you might encounter while using FxBlox and the Fula ecosystem.
44

55
## Common Issues
66

‎docs/getting-started-testnet.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ To get started, you'll need the following equipment:
1616
- For RK1 bloxes: internal m.2 nvme drive, external storage as mentioned above, or [framework expansion cards](https://frame.work/marketplace/expansion-cards)
1717
- Optional: USB-C to ethernet adaptors and USB-C to HDMI for additional connectivity
1818

19-
Functionland does not get any kickback or royalties from the sale of Framework expansion cards. We recommend them because we designed the FxBlox case and modularity around their small form factor standard.
19+
No kickback or royalties were received from the sale of Framework expansion cards. They are recommended because the FxBlox case and modularity were designed around their small form factor standard.
2020

2121
## 2. Identifying Your Blox
2222
It is important you know which FxBlox you have before you move onto the setup stage! It will determine which route you follow, how you get support, and what software is compatible with your device. Checkout the [How To Identify Your FxBlox](/functionyard/hardware/fxblox-hardware) guide to learn more!

‎docs/index.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -23,15 +23,15 @@ Which is when we realized, there was no single chain agnostic token we can use t
2323

2424
### Enter $FULA token
2525

26-
**$FULA** will be the catalyst for keeping the infrastructure online at all times and getting users to store their photos and video, for as long as they want. Storage providing and compute providers are two sides of the same coin. Providers require payment for offering their service to the public. And consumers need a corresponding way to pay for said services.
26+
**$FULA** is intended to keep the infrastructure online and getting users to store their photos and video, for as long as they want. Storage providing and compute providers are two sides of the same coin. Providers require payment for offering their service to the public. And consumers need a corresponding way to pay for said services.
2727

2828
### Enter [BAS](./introduction/bas)
2929

30-
The first uniform **Blockchain Attached Storage (BAS)** device was created. As a provider, you can use your storage device(s) to completely own your data and gain rewards for offering up your extra storage to the public. And as a consumer, can pay-as-you-go! It'll be like you have access to infinite storage and just pay for what you need to keep your data alive for as long as you like.
30+
The first uniform **Blockchain Attached Storage (BAS)** device was created. As a provider, you can use your storage device(s) to completely own your data and gain rewards for offering up your extra storage to the public.
3131

3232
### Enter [FxBlox](./introduction/blox)
3333

34-
FxBlox, or Blox, is the brand-new hardware that is empowering it all. Beautiful design, power-efficient board, and next-gen processing is not gate-kept by inflated pricing. Bloxes are competitively priced and offer the **<u>lowest</u>** barrier to entry in any decentralized storage blockchain. The network is designed to scale vertically and horizontally.
34+
FxBlox, or Blox, is the brand-new hardware that is empowering it all. Beautiful design, power-efficient board, and next-gen processing is not gate-kept by inflated pricing. Bloxes offer a low barrier to entry in decentralized storage. The network is designed to scale vertically and horizontally.
3535

3636
### Enter [Fula API](./api-intro)
3737

0 commit comments

Comments
 (0)