From 25899bc54f6b1642ca68aedef945d4232484f2cb Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Wed, 23 Apr 2025 16:52:25 +0200 Subject: [PATCH 1/6] fix: typo --- src/content/blog/announcements/Fleek-ElizaOS-autofun/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/blog/announcements/Fleek-ElizaOS-autofun/index.md b/src/content/blog/announcements/Fleek-ElizaOS-autofun/index.md index dcbd836d5..95bc2d364 100644 --- a/src/content/blog/announcements/Fleek-ElizaOS-autofun/index.md +++ b/src/content/blog/announcements/Fleek-ElizaOS-autofun/index.md @@ -56,7 +56,7 @@ There’s a deeper alignment here too. Eliza and Fleek both share a vision of ag That’s why this partnership will continue to grow and evolve. -Eliza helps define the agent logic, framework and OS. Fleek provides the infrastructure and platform to make it easy to create and manage the agents . Auto.fun becomes the place where the agents go to launch and activate their communities. +Eliza helps define the agent logic, framework and OS. Fleek provides the infrastructure and platform to make it easy to create and manage the agents. Auto.fun becomes the place where the agents go to launch and activate their communities. It’s not just a better launchpad. It’s a new standard for launching the next wave of crypto x AI projects, and we are proud to be involved. From 47a1874ec51cfa5ca110b63551cd92497558f342 Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Wed, 23 Apr 2025 16:55:16 +0200 Subject: [PATCH 2/6] fix: typo --- src/utils/url.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/utils/url.ts b/src/utils/url.ts index 054b4d648..03af6c3ac 100644 --- a/src/utils/url.ts +++ b/src/utils/url.ts @@ -20,7 +20,7 @@ export const getTopLevelDomain = (url: string) => { // The only expected hostnames // are a maximum of three levels - // at time of writting + // at time of writing // e.g. staging -> fleek-xyz-staging.on-fleek.app // and prod -> fleek.xyz const topLevelDomain = hostname.split('.').slice(-2).join('.'); From 2783ed97616e15d0359e7d04c05c1d625cb8cd1d Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Wed, 23 Apr 2025 16:56:22 +0200 Subject: [PATCH 3/6] fix: typo --- .../blog/announcements/fleek-xyz-architecture-overview/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/blog/announcements/fleek-xyz-architecture-overview/index.md b/src/content/blog/announcements/fleek-xyz-architecture-overview/index.md index c08820621..7cbbe14ef 100644 --- a/src/content/blog/announcements/fleek-xyz-architecture-overview/index.md +++ b/src/content/blog/announcements/fleek-xyz-architecture-overview/index.md @@ -39,7 +39,7 @@ When new services/protocols become available (maybe Akash or Arweave 👀), they ![Fleek.xyz Platform types and services](https://storageapi.fleek.co/fleek-team-bucket/Blogs/xyz-arch-services.png) -Going one level deeper, we have Fleek services. Each service is independent of each other and together are accesible from all of the four core building blocks (see diagram above). +Going one level deeper, we have Fleek services. Each service is independent of each other and together are accessible from all of the four core building blocks (see diagram above). **The key word here is independent**. Internally, independent services mean that we can move fast, without worrying about how changes might affect other services or the teams building them. It also means that projects like templates (yes, definitely coming in the future) are able to be bootstrapped to production way quicker than before. From d91c3c6e7b0e9559fb7eb2c9ad01727dfb10b829 Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Wed, 23 Apr 2025 16:57:06 +0200 Subject: [PATCH 4/6] fix: typo --- scripts/check-file-size.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/check-file-size.ts b/scripts/check-file-size.ts index 8a1b733bc..6a8904222 100755 --- a/scripts/check-file-size.ts +++ b/scripts/check-file-size.ts @@ -47,7 +47,7 @@ files.forEach((file) => { ); console.log( - '💡 For lenghty video content is much preferred to upload to a proper video streaming service, such as YouTube due to large file size. Please consider uploading to YouTube and using the video source-code snippet.', + '💡 For lengthy video content it is much preferred to upload to a proper video streaming service, such as YouTube due to large file size. Please consider uploading to YouTube and using the video source-code snippet.', ); process.exit(1); From 7c701e0016a00933dc4b70f9536546cbb2583aea Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Wed, 23 Apr 2025 16:58:41 +0200 Subject: [PATCH 5/6] fix: typo --- src/content/docs/fleek-dot-co.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/fleek-dot-co.mdx b/src/content/docs/fleek-dot-co.mdx index 0ebad8d48..cacc2918d 100644 --- a/src/content/docs/fleek-dot-co.mdx +++ b/src/content/docs/fleek-dot-co.mdx @@ -41,7 +41,7 @@ Assets that are unsuccessfully ported will be troubleshooted and flagged for som As part of the migration to Fleek.xyz and sunsetting of Fleek.co, the Fleek.co Storage SDK will also be sunset. This means that aside from migrating accounts, sites, and files, developers will also want to switch any previous references to the Fleek.co SDK in their codebase to the new Fleek.xyz SDK. This will ensure applications and projects continue to be fully functional without any hiccups post-sunset and deprecation of Fleek.co. -Throughout the migration, we will make sure you have all the tools, information, and time to make the change comfortably and confidently. Expect to see detailed guides and white-glove support on both manual and automated migration options. As mentioned, the whole process will be as as frictionless and abstracted away from your user experience as possible. +Throughout the migration, we will make sure you have all the tools, information, and time to make the change comfortably and confidently. Expect to see detailed guides and white-glove support on both manual and automated migration options. As mentioned, the whole process will be as frictionless and abstracted away from your user experience as possible. For those who want to get familiar with the new Fleek.xyz platform early, feel free to reach out and we’ll get you access to the beta. For the latest updates and support through this process, join our Discord community [here](https://discord.gg/fleek). ## Looking ahead From c93deb2a9a3435e826c33e6e4ea09ec2ec5b47a9 Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Wed, 23 Apr 2025 17:00:21 +0200 Subject: [PATCH 6/6] fix: typo --- src/content/docs/SDK/IPFS/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/SDK/IPFS/index.md b/src/content/docs/SDK/IPFS/index.md index 78efdfb6c..a2b23f6a8 100644 --- a/src/content/docs/SDK/IPFS/index.md +++ b/src/content/docs/SDK/IPFS/index.md @@ -13,7 +13,7 @@ tags: # IPFS -The Fleek Platform SDK helps you pin files to IPFS. The Interplanetary File system (IPFS) is a distributed file storage protocol that allow computers all over the globe to store and serve files as part of a giant peer-to-peer network. +The Fleek Platform SDK helps you pin files to IPFS. The Interplanetary File system (IPFS) is a distributed file storage protocol that allows computers all over the globe to store and serve files as part of a giant peer-to-peer network. :::warn We're transitioning from using the IPFS service to our new Storage service. To help you make this change smoothly, there's a grace period and we've included warnings within our SDK code. We recommend reviewing our [Storage documentation](/docs/sdk/storage) to understand how to switch to the Storage service. You should start utilizing the Storage service over the IPFS service.