Skip to content

Commit 41d1b46

Browse files
committed
chore: minor tweaks
1 parent 2d9931e commit 41d1b46

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

src/pages/build/4_entries.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,8 @@ tocData:
3030
href: reference
3131
---
3232

33+
An Entry is structured data written to an Agent's source chain via a CreateEntry or UpdateEntry Action.
34+
3335
## Define an Entry Type
3436

3537
An EntryType can be any Rust struct that `serde` can serialize and deserialize.
@@ -227,13 +229,13 @@ Calling `delete_entry` does the following:
227229

228230
## Entry IDs
229231

230-
Coming from the centralized database world, you might be expecting an Entry to have a unique ID that can be used to reference it elsewhere.
232+
Coming from centralized software architectures, you might be expecting an Entry to have a unique ID that can be used to reference it elsewhere.
231233

232-
Instead, holochain uses hashes to reference content. In practice, different kinds of hashes have different meaning and suitability to use as an identifier.
234+
Instead, Holochain uses hashes to reference content. In practice, different kinds of hashes have different meaning and suitability to use as an identifier.
233235

234-
To identify the *contents* of an Entry, use the entry's `EntryHash`. Remember that entry contents will collide in the DHT if the exact same entry is published multiple times.
236+
To identify the *contents* of an Entry, use the entry's `EntryHash`. Remember that identical entry contents will collide in the DHT.
235237

236-
A common pattern to identify an *instance* of an Entry (i.e. an Entry authored by a specific agent at a specific time) is to use the `ActionHash` of the Create action which created the original entry. This can be a persistant way to identify the entry, even when it is updated, as other agents can query for updates themselves to discover the latest version.
238+
A common pattern to identify an *instance* of an Entry (i.e. an Entry authored by a specific agent at a specific time) is to use the `ActionHash` of the Create action which created the original entry. This can be a persistent way to identify the entry, even when it is updated, as other agents can query for updates themselves to discover the latest version.
237239

238240
## Community CRUD Libraries
239241

0 commit comments

Comments
 (0)