Skip to content

Commit f5a0c71

Browse files
shayne-fletchermeta-codesync[bot]
authored andcommitted
fix numbering (#1819)
Summary: Pull Request resolved: #1819 just fixes some numbering issues. Reviewed By: thedavekwon Differential Revision: D86762620 fbshipit-source-id: 0036fef3ad4cda009d6c3b9cb46c3b1744e705f8
1 parent 847d91b commit f5a0c71

File tree

5 files changed

+6
-6
lines changed

5 files changed

+6
-6
lines changed

docs/source/books/hyperactor-mesh-book/src/meshes/bootstrapping-doing-real-work.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# 4. Doing real work (hosts → procs → actors)
1+
# §4 Doing real work (hosts → procs → actors)
22

33
We can now line up the rest of `bootstrap_cannonical_simple` and see that the remaining calls are just "use the host we just created."
44

@@ -10,7 +10,7 @@ let host_mesh = HostMesh::allocate(&instance, Box::new(alloc), "test", None)
1010
.unwrap();
1111
```
1212

13-
was the part we just broke down in §1.4 — it consumed the allocation, talked to the children, ran the trampoline, and gave us a real `HostMesh`.
13+
was the part we just broke down in §3 — it consumed the allocation, talked to the children, ran the trampoline, and gave us a real `HostMesh`.
1414

1515
The test immediately does two more things:
1616

docs/source/books/hyperactor-mesh-book/src/meshes/bootstrapping-from-python.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# Boostrapping from Python
1+
# §5 Boostrapping from Python
22

33
So far we described the Rust side: there is a host, the host has a `HostMeshAgent`, and we send `CreateOrUpdate<ProcSpec>` etc. That's the control plane.
44

docs/source/books/hyperactor-mesh-book/src/meshes/bootstrapping-hostmesh-from-allocation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# 3. HostMesh from an allocation (what `HostMesh::allocate(...)` actually does)
1+
# §3 HostMesh from an allocation (what `HostMesh::allocate(...)` actually does)
22

33
At this point we already have:
44

docs/source/books/hyperactor-mesh-book/src/meshes/bootstrapping-proc-and-instance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
## 1. Proc and Instance (start from a Proc you control)
1+
## §1 Proc and Instance (start from a Proc you control)
22

33
We begin in a process that can already run hyperactor code and create an instance:
44

docs/source/books/hyperactor-mesh-book/src/meshes/bootstrapping-process-allocator.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# 2. Process allocator & v0 bootstrap (get something that can spawn processes)
1+
# §2 Process allocator & v0 bootstrap (get something that can spawn processes)
22

33
## 2. Get something that can spawn processes
44

0 commit comments

Comments
 (0)