nits

src/SUMMARY.md

@@ -7,7 +7,8 @@
   - [Installation](./install.md)
   - [Join the Network](./login.md)
 - [System Components](./system-components.md)
-  - [Processes](./process/processes.md)
+  - [Processes](./processes-overview.md)
+    - [Process Semantics](./process/processes.md)
     - [Capability-Based Security](./process/capabilities.md)
     - [Startup, Spindown, and Crashes](./process/startup.md)
     - [Extensions](./process/extensions.md)

src/build-and-deploy-an-app.md

@@ -1,10 +1,9 @@
 # My First Kinode Application
 
-Welcome!
 In these tutorials, you'll setup your development environment and learn about the `kit` tools.
 You'll learn about templates and also walk through writing an application from the group up, backend and frontend.
 And finally, you'll learn how to deploy applications through the Kinode app store.
 
 For the purposes of this documentation, terminal commands are provided as-is for ease of copying EXCEPT when the output of the command is also shown.
 In that case, the command is prepended with a `$ ` to distinguish the command from the output.
-The `$ ` should not be copied into the terminal.
+The `$ ` should not be copied into the terminal.

src/process/processes.md

@@ -1,4 +1,4 @@
-# Processes
+# Process Semantics
 
 ### Overview
 
@@ -30,7 +30,7 @@ process_one:my_cool_software:publisher_node.os
 [Addresses](https://docs.rs/kinode_process_lib/latest/kinode_process_lib/kinode/process/standard/struct.Address.html) look like:
 
 ```
-[node]:[process_name]:[package_name]:[publisher_node]
+[node]@[process_name]:[package_name]:[publisher_node]
 some_user.os@process_one:my_cool_software:publisher_node.os
 ```
 
@@ -188,5 +188,5 @@ Kinode processes are Wasm components that have certain imports and exports so th
 Pragmatically, processes can be compiled using the [`kit` tools](https://github.com/kinode-dao/kit).
 
 
-The long term goal of Kinode is, using [WASI](https://wasi.dev/), to provide a secure, sandboxed environment for Wasm components to make use of the kernel features described in this document. 
+The long term goal of Kinode is, using [WASI](https://wasi.dev/), to provide a secure, sandboxed environment for Wasm components to make use of the kernel features described in this document.
 Further, Kinode has a Virtual File System ([VFS](../files.md)) which processes can interact with to access files on a user's machine, and in the future WASI could also expose access to the filesystem for Wasm components directly.

src/processes-overview.md

@@ -0,0 +1,8 @@
+# Processes
+
+Processes are independent pieces of Wasm code running on Kinode OS.
+They can either be persistent, in which case they have in-memory state, or temporary, completing some specific task and returning.
+They have access to long-term storage, like the filesystem or databases.
+They can communicate locally and over the Kinode network.
+They can access the internet via HTTP or WebSockets.
+And these abilities can be controlled using a capabilities security model.