Found a typo?

[jamiepine]

Any changes to spelling, grammar or the wording structure of the README, code comments or documentation can be suggested here to avoid pull request clutter. Thank you!

[yadunandanbhat]

The "links will be added once release available" is wrong grammar, it should be "Links will be added once the release is available". And the note about the app being in development is added twice, which is redundant. Can i open a pr for this?

[maxichrome]

And in the monorepo structure, some links point to their respective websites, while some point to the readme itself, which is kinda odd.
See below image.

Every link in the app sub heading point to their respective website, but everything else just points to "https://github.com/spacedriveapp/spacedrive#"

The second notice you brought up earlier actually addresses this.

[jamiepine]

ce058ab
34ebbf4

[maxichrome]

ce058ab
34ebbf4

That second commit removes the notice about links being broken

[jamiepine]

they should be fixed asap

[yadunandanbhat]

cool!

[leozaffre]

The link to the contributing guide under Developer Guide is broken.
https://github.com/spacedriveapp

[ghost]

Feild should be field here: https://github.com/spacedriveapp/spacedrive/blob/main/core/prisma/schema.prisma#L183

[s4mbre]

README.md
Line 88
keybind should be key bind

docs/architecture/virtual-filesystem.md
Line 41
prioritised should be prioritized

docs/product/roadmap.md
Line 18
keybind should be key bind

[jamiepine]

I know "key bind" is probably grammatically correct, but I think it looks awkward and I prefer using it as a single word.

[hulxv]

I suggest making a GitHub workflow by using typos to check if there are typos or not. I think that's better.

[oscartbeaumont]

We are gonna do this at some point. Currently, we have a lefthook script for it but it doesn't seem to be catching typos very well.

[schneedotdev]

Line 62
"VSFS" should be "VDFS" at "VSFS is not restricted to a single machine

[z1cheng]

Typos:

1. core/Cargo.toml, Line 11: controlls -> controls
2. core/src/job/jobs.rs, Line 46 and Line 55: internal_reciever -> internal_receiver
3. core/src/util/db.rs, Line 18: occured -> occurred

You can also check this PR

[Brendonovich]

5e30331

[christophermorin]

Hello,
A few typos in some of the docs:

1. README, Line 114 - 'completly' -> completely
2. docs/architecture/search, Line 5 - 'simotanious' -> simultaneous
3. docs/architecture/spaces, Line 3b - 'spacially' -> spatially
4. docs/architecture/sync, Line 5 - 'Logicial' -> Logical

[Brendonovich]

5e30331

[JJJJJJJJJJJJJJJl]

@introduction.md - Line 14

Fixing typo where "optimized" is miswritten as "optimizes".

Also, defining the word decentralized as a system in which information is shared (and trusted) across multiple network users, I don't think describing Spacedrive as a decentralized design is the most accurate move. But, this is probably minor.

[jamiepine]

I agree. I diverted from referring to it as "distributed" because I felt that if the nodes synchronize without a master then it must be "decentralized", but that isn't entirely true. Our data sync design works similarly to consensus, all the nodes will be eventually consistent without a server or master node to resolve conflicts — however I understand that decentralized typically refers to blockchain apps, which this certainly not. Thanks for bringing this up, appreciate it.

[simonmurdock]

https://www.spacedrive.com/docs/product/getting-started/introduction

"Create photo albums that you'll never loose, effortlessly"

[Brendonovich]

'loose' means not being contained, rigid or confined. 'lose' is the right word for that sentence.

[shoebob15]

In the node docs, the hyperlink that is supposed to go to the nodes doc instead links back to the current page. In the source docs, it doesn't link to anything: A library is the database that Spacedrive stores all file structures and metadata. It can be synchronized with other [Nodes]().. This also happens on the website.

[utkubakir]

docs are wip right now, once we have some content, we will go over all links. Thanks!

[gBasil]

"its" should be "it's" in "and best of all, its open source and entirely free." in the file docs/product/getting-started/introduction.md.

[tomheaton]

README.md - Line 107:

- - `config`: `eslint` configurations (includes `eslint-config-next`, `eslint-config-prettier` and all `tsconfig.json` configs used throughout the monorepo.
+ - `config`: `eslint` configurations (includes `eslint-config-next`, `eslint-config-prettier` and all `tsconfig.json` configs used throughout the monorepo).

[utkubakir]

fixed, thank you

[Crilum]

Not sure where it is in the code, but this is definitely not correct grammar:

I think it might be supposed to say Scanned 2 more files or directories;?

[utkubakir]

fixed! thank you

[alexsmacd]

The Changelog link in the footer of SpaceDrive.com is broken. It should go to https://www.spacedrive.com/docs/changelog/alpha/0.1.4, but it links to https://www.spacedrive.com/docs/changelog/beta/0.1.0.

Question/Suggestion: Is there a way to setup a redirect so that https://www.spacedrive.com/docs/changelog/ goes to the latest version?

[utkubakir]

Yeah we should be to redirect users to latest changelog. Thanks for the suggestion!

[ParamBirje]

The "App Crashed" screen has the string "Check the console (CMD/CTRL + OPTION + i) for stack trace." which is generic for all operating systems.

Specifically on Win/Linux, the shortcut to open the console is assigned to CTRL+SHIFT+i, we need to add SHIFT in the message on the crash screen to make it consistent with the instructions in CONTRIBUTING.md

Thus making the new string "Check the console (CMD/CTRL + OPTION/SHIFT + i) for stack trace."

Can I put up a PR for it for this? The line in ErrorFallback.tsx

[utkubakir]

fixed, thank you!

[Raghav-45]

https://www.spacedrive.com/docs/product/guides/interface

Let's start by getting a clear understanding of the Spacedrive interface. Designed to mimic what you know and love with existing file explorers, but with powerful features and a universal desgin across operating systems.

Design spelling is wrong

[utkubakir]

fixed on #2317 thank you!

[David-Kyrat]

What ?

I detected a typo in actual code (./scripts/setup.sh) i don't know if i should report it here.

When?

• When using fedora , i.e. dnf gets detected when running ./scripts/setup.sh

Where?

• On line 188 in

      # Tauri dependencies
      set -- openssl webkit2gtk4.1-devel openssl-dev curl wget file libappindicator-gtk3-devel librsvg2-devel libxdo-devel dbus-devel

openssl-dev should be openssl-devel (because dev packages are called "devel" on rpm based systems.)

like this

      set -- openssl webkit2gtk4.1-devel openssl-devel curl wget file libappindicator-gtk3-devel librsvg2-devel libxdo-devel dbus-devel

How am I sure it's indeed a typo

• When i first ran the script, dnf gave me an error message like "package openssl-dev" does not exist.
• After doing the replacement on line 188, i ran the setup script again and it appear to have worked ( I got the message "Your machine has been setup for Spacedrive development!" at the end)

[iLynxcat]

@HeavenVolkoff @matheus-consoli can one of you confirm & possibly take a few minutes to resolve this?

[randompersonperson]

In https://github.com/spacedriveapp/spacedrive/blob/main/docs/developers/architecture/vdfs.mdx, the last word should be "accommodate", not " accomedate".

[valeriewong052]

Fixed, thanks!

[randompersonperson]

In https://github.com/spacedriveapp/spacedrive/blob/main/docs/developers/architecture/libraries.mdx,
it should be "You must create a library to use Spacedrive. Users can also choose to create more libraries, such as ones specifically for work. Spacedrive will run all your libraries in unison."

instead of "You must create a library to use Spacedrive. Users can also choose to create more librariesm, such as ones specifically for work. Spacedrive will run all your libraries in unison."

[valeriewong052]

Fixed!

[iLynxcat]

Locking and closing this discussion — in a PR I'll be submitting shortly tonight we'll take typo reports via GitHub Issues