From 55a98272be3378c31e7d5ba0a0952d427ea7670d Mon Sep 17 00:00:00 2001
From: "Peter J. Keleher" <keleher@cs.umd.edu>
Date: Sun, 29 Oct 2023 16:44:58 -0400
Subject: [PATCH] auto

---
 p4.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/p4.md b/p4.md
index 8698574..f3430d9 100644
--- a/p4.md
+++ b/p4.md
@@ -80,16 +80,16 @@ characters. The path to the root is "". A path from the
 root to the a leaf in a depth 4 (height 3 in the usual nomenclature)
 will be a string of length 3, e.g.: "Z4A". 
 
-The build RPC will return the *blob tree hash* (hash of top node in
+The *build* RPC will return the *blob tree hash* (hash of top node in
 the merkle tree). A server saves all blob trees it has built in
 response to remote requests, never garbage-collecting. The build RPC should also return
 the total number of blob hashes in the tree.
 
-Since the trees are persistent, a client can then navigate the remote tree
+A remote build trees is persistent in the remote server's memory, so a client can then navigate the remote tree
 via the *path* RPC. Arguments are the blob tree hash and a path
 string. The return value will include an array of *sigs* that describe
 the children of the node defined by the blob tree hash and the
-path. The children are blob hashes if the node is a leaf, or hashes
+path. The children are blob hashes (*sigs*) if the node is a leaf, or hashes
 of hashes otherwise. 
 
 *The hash of a node is defined as the hash of the concatenation of the
-- 
GitLab