Update walletFS product casing

src/pages/index.mdx

@@ -32,7 +32,7 @@ description: Documentation for Bloom, the agentic Ethereum wallet mounted as a v
   }
 `}</style>
 
-Bloom is an **agentic Ethereum wallet mounted as a virtual filesystem**.
+/bloom walletFS is an **agentic Ethereum wallet mounted as a virtual filesystem**.
 
 Reads are blockchain queries. Writes are transaction intents. The main interface is an ordinary directory that humans and agents can inspect with normal filesystem tools like `ls`, `cat`, and file writes.
 

src/pages/introduction/what-is-bloom.mdx

@@ -1,6 +1,6 @@
 # What is Bloom?
 
-Bloom gives agents a safe wallet workspace for Ethereum and EVM chains.
+Bloom is a framework for creating agent-safe software components. The first application of Bloom is an agentic Ethereum wallet. We call this walletFS.
 
 <div style={{ position: 'relative', width: '100%', paddingTop: '56.25%', margin: '1.5rem 0' }}>
   <iframe
@@ -27,7 +27,7 @@ The first Bloom application is an agentic wallet:
 
 ## Broader direction
 
-Bloom’s broader architecture extends this filesystem model to small, composable, verifiable programs called Petals. The wallet is the first concrete wedge: it makes the abstraction useful immediately for safe agent-controlled onchain workflows.
+Bloom’s broader architecture extends this filesystem model to small, composable, verifiable programs called Petals. walletFS is the first use case of Petals: it makes the abstraction useful immediately for safe agent-controlled onchain workflows.
 
 ## Status
 

src/pages/petals/overview.mdx

@@ -4,7 +4,7 @@
 
 Petals are not ready for prime-time use. They are in active development, the APIs and runtime model may change, and the current documentation is primarily for Bloom developers rather than end users.
 
-Today, Petals should be understood as the path toward safe extensions to WalletFS: small, reviewable modules that can add capabilities behind Bloom’s policy, planning, and filesystem boundaries without asking agents to write custom signing or broadcast code.
+Today, Petals should be understood as the path toward safe extensions to walletFS: small, reviewable modules that can add capabilities behind Bloom’s policy, planning, and filesystem boundaries without asking agents to write custom signing or broadcast code.
 
 For an early example of a custom petal, see [`bloombook`](https://github.com/bloom-directory/bloombook). It is useful as a developer reference for how Petals can package new filesystem-backed capabilities, but it should be treated as experimental alongside the Petals runtime itself.
 

vocs.config.ts

@@ -20,12 +20,13 @@ export default defineConfig({
   rootDir: 'src/pages',
   renderStrategy: 'full-static',
   socials: [
-    { icon: 'github', link: 'https://github.com/bloom-directory' },
-    { icon: 'x', link: 'https://x.com/bloomdirectory' },
+    { icon: 'github', link: 'https://github.com/bloom-directory/' },
+    { icon: 'x', link: 'https://x.com/bloom_directory' },
+    { icon: 'telegram', link: 'https://t.me/bloom_directory' },
   ],
   topNav: [
     { text: 'Website', link: 'https://bloom.directory' },
-    { text: 'GitHub', link: 'https://github.com/bloom-directory' },
+    { text: 'GitHub', link: 'https://github.com/bloom-directory/bloom' },
   ],
   sidebar: [
     { text: 'Overview', link: '/' },