docs: fix daily docs audit findings

docs/docs/00100-intro/00100-getting-started/00400-key-architecture.md

@@ -345,9 +345,18 @@ ctx.procedures.makeRequest().then(
 </TabItem>
 <TabItem value="csharp" label="C#">
 
-C# modules currently cannot define procedures. Support for defining procedures in C# modules will be released shortly.
+C# modules can define procedures:
 
-A C# [client](#client) can call a procedure defined by a Rust or TypeScript module:
+```csharp
+[SpacetimeDB.Procedure]
+public static string MakeRequest(ProcedureContext ctx)
+{
+    // ...
+    return "result";
+}
+```
+
+A C# [client](#client) can call a procedure defined by a module:
 
 ```csharp
 void Main()
@@ -384,7 +393,7 @@ Because procedures are unstable, Rust modules that define them must opt in to th
 
 ```toml
 [dependencies]
-spacetimedb = { version = "1.x", features = ["unstable"] }
+spacetimedb = { version = "2.*", features = ["unstable"] }
 ```
 
 Then, that module can define a procedure:
@@ -436,7 +445,7 @@ Use the other tabs (TypeScript/C#/Rust/Unreal C++/Blueprint) for client call exa
 </TabItem>
 <TabItem value="cpp-unreal" label="Unreal C++">
 
-An Unreal C++ [client](#client) can call a procedure defined by a Rust or TypeScript module:
+An Unreal C++ [client](#client) can call a procedure defined by a module:
 
 ```cpp
 {
@@ -468,7 +477,7 @@ void AGameManager::OnMakeRequestComplete(const FProcedureEventContext& Context,
 </TabItem>
 <TabItem value="blueprint" label="Unreal Blueprint">
 
-An Unreal [client](#client) can call a procedure defined by a Rust or TypeScript module:
+An Unreal [client](#client) can call a procedure defined by a module:
 
 ![MakeRequest without callback](/images/unreal/intro/ue-blueprint-makerequest-nocallback.png)
 

docs/docs/00100-intro/00300-tutorials/00100-chat-app.md

@@ -2042,7 +2042,10 @@ void PrintMessage(RemoteTables tables, Message message)
 
 #### Warn if our name was rejected
 
-We can also register callbacks to run each time a reducer is invoked. We register these callbacks using the `OnReducerEvent` method of the `Reducer` namespace, which is automatically implemented for each reducer by `spacetime generate`.
+We can also register callbacks for reducer results. We register these callbacks
+using generated events on `conn.Reducers`, such as `conn.Reducers.OnSetName`
+and `conn.Reducers.OnSendMessage`, which are automatically implemented for
+each reducer by `spacetime generate`.
 
 Each reducer callback takes one fixed argument:
 
@@ -2061,7 +2064,11 @@ These callbacks will be invoked in one of two cases:
 
 Note that a status of `Failed` or `OutOfEnergy` implies that the caller identity is our own identity.
 
-We already handle successful `SetName` invocations using our `User.OnUpdate` callback, but if the module rejects a user's chosen name, we'd like that user's client to let them know. We define a function `Reducer_OnSetNameEvent` as a `Reducer.OnSetNameEvent` callback which checks if the reducer failed, and if it did, prints an error message including the rejected name.
+We already handle successful `SetName` invocations using our `User.OnUpdate`
+callback, but if the module rejects a user's chosen name, we'd like that user's
+client to let them know. We define a function `Reducer_OnSetNameEvent` and
+register it with `conn.Reducers.OnSetName`; the callback checks if the reducer
+failed, and if it did, prints an error message including the rejected name.
 
 We'll test both that our identity matches the sender and that the status is `Failed`, even though the latter implies the former, for demonstration purposes.
 

docs/docs/00100-intro/00300-tutorials/00300-unity-tutorial/00400-part-3.md

@@ -721,7 +721,7 @@ const START_PLAYER_MASS: i32 = 15;
 #[spacetimedb::reducer]
 pub fn enter_game(ctx: &ReducerContext, name: String) -> Result<(), String> {
     log::info!("Creating player with name {}", name);
-    let mut player: Player = ctx.db.player().identity().find(ctx.sender).ok_or("")?;
+    let mut player: Player = ctx.db.player().identity().find(ctx.sender()).ok_or("")?;
     let player_id = player.player_id;
     player.name = name;
     ctx.db.player().identity().update(player);
@@ -786,11 +786,11 @@ pub fn disconnect(ctx: &ReducerContext) -> Result<(), String> {
         .db
         .player()
         .identity()
-        .find(&ctx.sender)
+        .find(&ctx.sender())
         .ok_or("Player not found")?;
     let player_id = player.player_id;
     ctx.db.logged_out_player().insert(player);
-    ctx.db.player().identity().delete(&ctx.sender);
+    ctx.db.player().identity().delete(&ctx.sender());
 
     // Remove any circles from the arena
     for circle in ctx.db.circle().player_id().filter(&player_id) {

docs/docs/00100-intro/00300-tutorials/00400-unreal-tutorial/00300-part-2.md

@@ -655,7 +655,7 @@ spacetime generate --lang unrealcpp --uproject-dir .. --unreal-module-name black
 This will generate a set of files in the `blackholio/Source/blackholio/Private/ModuleBindings` and `blackholio/Source/blackholio/Public/ModuleBindings` directories which contain the code generated types and reducer functions that are defined in your module, but usable on the client.
 
 :::note
-`--uproject-dir` is straightforward as the path to the .uproject file. `--unreal-module-name` is the name of the Unreal module which in most projects is the name of the project, in this case `blackholio`.
+`--uproject-dir` is the path to the Unreal project directory that contains the `.uproject` file. `--unreal-module-name` is the name of the Unreal module, which in most projects is the name of the project, in this case `blackholio`.
 :::
 
 :::warning

docs/docs/00100-intro/00300-tutorials/00500-godot-tutorial/00400-part-3.md

@@ -721,7 +721,7 @@ const START_PLAYER_MASS: i32 = 15;
 #[spacetimedb::reducer]
 pub fn enter_game(ctx: &ReducerContext, name: String) -> Result<(), String> {
     log::info!("Creating player with name {}", name);
-    let mut player: Player = ctx.db.player().identity().find(ctx.sender).ok_or("")?;
+    let mut player: Player = ctx.db.player().identity().find(ctx.sender()).ok_or("")?;
     let player_id = player.player_id;
     player.name = name;
     ctx.db.player().identity().update(player);
@@ -786,11 +786,11 @@ pub fn disconnect(ctx: &ReducerContext) -> Result<(), String> {
         .db
         .player()
         .identity()
-        .find(&ctx.sender)
+        .find(&ctx.sender())
         .ok_or("Player not found")?;
     let player_id = player.player_id;
     ctx.db.logged_out_player().insert(player);
-    ctx.db.player().identity().delete(&ctx.sender);
+    ctx.db.player().identity().delete(&ctx.sender());
 
     // Remove any circles from the arena
     for circle in ctx.db.circle().player_id().filter(&player_id) {

docs/docs/00200-core-concepts/00100-databases/00500-cheat-sheet.md

@@ -775,7 +775,7 @@ SPACETIMEDB_VIEW(std::optional<PlayerCount>, player_count, Public, AnonymousView
 ```typescript
 ctx.db                  // Database access
 ctx.sender              // Identity of caller
-ctx.connectionId        // ConnectionId | undefined
+ctx.connectionId        // ConnectionId | null
 ctx.timestamp           // Timestamp
 ctx.databaseIdentity    // Module's identity
 ```

docs/docs/00200-core-concepts/00200-functions/00300-reducers/00300-reducers.md

@@ -546,7 +546,7 @@ import { ScheduleAt } from 'spacetimedb';
 import { schema, t, table } from 'spacetimedb/server';
 
 // Define a schedule table for the procedure
-const fetchSchedule = table(
+const fetch_schedule = table(
   { name: 'fetch_schedule', scheduled: (): any => fetch_external_data },
   {
     scheduled_id: t.u64().primaryKey().autoInc(),
@@ -555,12 +555,12 @@ const fetchSchedule = table(
   }
 );
 
-const spacetimedb = schema({ fetchSchedule });
+const spacetimedb = schema({ fetch_schedule });
 export default spacetimedb;
 
 // The procedure to be scheduled
 export const fetch_external_data = spacetimedb.procedure(
-  { arg: fetchSchedule.rowType },
+  { arg: fetch_schedule.rowType },
   t.unit(),
   (ctx, { arg }) => {
     const response = ctx.http.fetch(arg.url);
@@ -571,7 +571,7 @@ export const fetch_external_data = spacetimedb.procedure(
 
 // From a reducer, schedule the procedure by inserting into the schedule table
 export const queueFetch = spacetimedb.reducer({ url: t.string() }, (ctx, { url }) => {
-  ctx.db.fetchSchedule.insert({
+  ctx.db.fetch_schedule.insert({
     scheduled_id: 0n,
     scheduled_at: ScheduleAt.interval(0n), // Run immediately
     url,

docs/docs/00200-core-concepts/00200-functions/00300-reducers/00400-reducer-context.md

@@ -131,7 +131,7 @@ Every reducer invocation has an associated caller identity.
 <TabItem value="typescript" label="TypeScript">
 
 ```typescript
-import { schema, table, t, type Identity } from 'spacetimedb/server';
+import { schema, table, t } from 'spacetimedb/server';
 
 const player = table(
   { name: 'player', public: true },
@@ -257,7 +257,7 @@ SPACETIMEDB_REDUCER(update_score, ReducerContext ctx, uint32_t new_score) {
 The connection ID identifies the specific client connection that invoked the reducer. This is useful for tracking sessions or implementing per-connection state.
 
 :::note
-The connection ID may be `None`/`null`/`undefined` for reducers invoked by the system (such as scheduled reducers or lifecycle reducers) or when called via the CLI without specifying a connection.
+The connection ID may be absent for reducers invoked by the system (such as scheduled reducers or lifecycle reducers) or when called via the CLI without specifying a connection. In TypeScript modules, `ctx.connectionId` is `ConnectionId | null`.
 :::
 
 ### Timestamp
@@ -324,7 +324,7 @@ Scheduled reducers and procedures are private by default in SpacetimeDB 2.x, so
 ```typescript
 import { schema, table, t } from 'spacetimedb/server';
 
-const scheduledTask = table(
+const scheduled_task = table(
   { name: 'scheduled_task', scheduled: (): any => send_reminder },
   {
     taskId: t.u64().primaryKey().autoInc(),
@@ -333,10 +333,10 @@ const scheduledTask = table(
   }
 );
 
-const spacetimedb = schema({ scheduledTask });
+const spacetimedb = schema({ scheduled_task });
 export default spacetimedb;
 
-export const send_reminder = spacetimedb.reducer({ arg: scheduledTask.rowType }, (_ctx, { arg }) => {
+export const send_reminder = spacetimedb.reducer({ arg: scheduled_task.rowType }, (_ctx, { arg }) => {
   console.log(`Reminder: ${arg.message}`);
 });
 ```
@@ -349,20 +349,20 @@ using SpacetimeDB;
 
 public static partial class Module
 {
-    [SpacetimeDB.Table(Accessor = "ScheduledTask", Scheduled = nameof(SendReminder))]
+    [SpacetimeDB.Table(Accessor = "ScheduledTask", Scheduled = nameof(SendReminder), ScheduledAt = nameof(ScheduledAt))]
     public partial struct ScheduledTask
     {
         [SpacetimeDB.PrimaryKey]
         [SpacetimeDB.AutoInc]
-        public ulong taskId;
-        public ScheduleAt scheduledAt;
-        public string message;
+        public ulong TaskId;
+        public ScheduleAt ScheduledAt;
+        public string Message;
     }
 
     [SpacetimeDB.Reducer]
     public static void SendReminder(ReducerContext _ctx, ScheduledTask task)
     {
-        Log.Info($"Reminder: {task.message}");
+        Log.Info($"Reminder: {task.Message}");
     }
 }
 ```
@@ -426,7 +426,7 @@ SPACETIMEDB_REDUCER(send_reminder, ReducerContext _ctx, ScheduledTask task) {
 | `db`           | `DbView`                   | Access to the module's database tables          |
 | `sender`       | `Identity`                 | Identity of the caller                          |
 | `senderAuth`   | `AuthCtx`                  | Authorization context for the caller (includes JWT claims and internal call detection) |
-| `connectionId` | `ConnectionId \| undefined`| Connection ID of the caller, if available       |
+| `connectionId` | `ConnectionId \| null`     | Connection ID of the caller, if available       |
 | `timestamp`    | `Timestamp`                | Time when the reducer was invoked               |
 | `random`       | `Random`                   | Random number generator (deterministic, seeded by SpacetimeDB) |
 </TabItem>

docs/docs/00200-core-concepts/00200-functions/00300-reducers/00500-lifecycle.md

@@ -385,5 +385,5 @@ Reducers can be triggered at specific times using schedule tables. See [Schedule
 :::info Scheduled Reducer Context
 Scheduled reducer calls originate from SpacetimeDB itself, not from a client. Therefore:
 - `ctx.sender()` will be the module's own identity
-- `ctx.connection_id()` will be `None`/`null`/`undefined`
+- The connection ID will be absent (`null` in TypeScript, `null` in C#, `None` in Rust, and `std::nullopt` in C++)
 :::

docs/docs/00200-core-concepts/00200-functions/00400-procedures.md

@@ -128,20 +128,20 @@ This means there's no `ctx.db` field to access the database.
 Instead, procedure code must manage transactions explicitly with `ProcedureCtx.withTx`.
 
 ```typescript
-const myTable = table(
+const my_table = table(
     { name: "my_table" },
     {
         a: t.u32(),
         b: t.string(),
     },
 )
 
-const spacetimedb = schema({ myTable });
+const spacetimedb = schema({ my_table });
 export default spacetimedb;
 
 export const insert_a_value = spacetimedb.procedure({ a: t.u32(), b: t.u32() }, t.unit(), (ctx, { a, b }) => {
     ctx.withTx(ctx => {
-        ctx.db.myTable.insert({ a, b });
+        ctx.db.my_table.insert({ a, b });
     });
     return {};
 })
@@ -328,7 +328,7 @@ export const maybe_insert_a_value = spacetimedb.procedure({ a: t.u32(), b: t.str
         if (a < 10) {
             throw new SenderError("a is less than 10!");
         }
-        ctx.db.myTable.insert({ a, b });
+        ctx.db.my_table.insert({ a, b });
     });
 })
 ```
@@ -1190,7 +1190,7 @@ A common use case for procedures is integrating with external APIs like OpenAI's
 import { schema, t, table, SenderError } from 'spacetimedb/server';
 import { TimeDuration } from 'spacetimedb';
 
-const aiMessage = table(
+const ai_message = table(
   { name: 'ai_message', public: true },
   {
     user: t.identity(),
@@ -1200,7 +1200,7 @@ const aiMessage = table(
   }
 );
 
-const spacetimedb = schema({ aiMessage });
+const spacetimedb = schema({ ai_message });
 export default spacetimedb;
 
 export const ask_ai = spacetimedb.procedure(
@@ -1235,7 +1235,7 @@ export const ask_ai = spacetimedb.procedure(
 
     // Store the conversation in the database
     ctx.withTx(txCtx => {
-      txCtx.db.aiMessage.insert({
+      txCtx.db.ai_message.insert({
         user: txCtx.sender,
         prompt,
         response: aiResponse,