Update documentation for accuracy and consistency

- Clarified terminology in create-graph.md, changing "in this flow" to "in this graph."
- Updated environment variable names in create-runtime.md for state manager URI and API key for better clarity.
- Adjusted import statements in register-node.md to include BaseNode for improved context.
- Standardized parameter naming in state-manager-setup.md by changing "api_key" to "key."

Author: nk-ag

docs/docs/exosphere/create-graph.md

@@ -103,7 +103,7 @@ Define the nodes in your workflow with their inputs and next nodes:
 
 - **`node_name`**: The class name of the node (must be registered)
 - **`namespace`**: The namespace where the node is registered
-- **`identifier`**: Unique identifier for the node in this flow
+- **`identifier`**: Unique identifier for the node in this graph
 - **`inputs`**: Input values for the node
 - **`next_nodes`**: Array of node identifiers that this node connects to
 
@@ -124,7 +124,7 @@ Use the `${{ ... }}` syntax to map outputs from previous nodes:
 **Mapping Syntax:**
 
 - **`${{ node_identifier.outputs.field_name }}`**: Maps output from a specific node
-- **`initial`**: Static value provided when the flow is triggered
+- **`initial`**: Static value provided when the graph is triggered
 - **Direct values**: String values. In v1, numbers/booleans must be string-encoded (e.g., "42", "true").
 ## Creating Graph Templates
 

docs/docs/exosphere/create-runtime.md

@@ -78,8 +78,8 @@ The `Runtime` class is the core component that manages the execution environment
 
 ### Optional Parameters
 
-- **`state_manager_uri`** (str | None): URI of the state manager service. If not provided, uses `EXOSPHERE_URI` environment variable.
-- **`key`** (str | None): API key for authentication. If not provided, uses `EXOSPHERE_KEY` environment variable.
+- **`state_manager_uri`** (str | None): URI of the state manager service. If not provided, uses `EXOSPHERE_STATE_MANAGER_URI` environment variable.
+- **`key`** (str | None): API key for authentication. If not provided, uses `EXOSPHERE_API_KEY` environment variable.
 - **`batch_size`** (int): Number of states to fetch per poll. Defaults to 16.
 - **`workers`** (int): Number of concurrent worker threads. Defaults to 4.
 - **`state_manager_version`** (str): State manager API version. Defaults to "v0".

docs/docs/exosphere/register-node.md

@@ -68,6 +68,9 @@ class Secrets(BaseModel):
 The runtime automatically validates your nodes:
 
 ```python hl_lines="19"
+from exospherehost import BaseNode
+from pydantic import BaseModel
+
 # ✅ Valid node
 class ValidNode(BaseNode):
     class Inputs(BaseModel):
@@ -103,7 +106,7 @@ class InvalidNode(BaseNode):
 Nodes are automatically registered when you start your runtime:
 
 ```python hl_lines="14"
-from exospherehost import Runtime
+from exospherehost import Runtime, BaseNode
 
 # Create your nodes
 class Node1(BaseNode):

docs/docs/exosphere/state-manager-setup.md

@@ -118,7 +118,7 @@ The state manager uri and key would be configured accordingly while setting up n
            name="YourWorkflow",
            nodes=[YourNodes],
            state_manager_uri="https://api.exosphere.host",
-           api_key="your-production-api-key"
+           key="your-production-api-key"
        ).start()
        ```