From 43082e3a7ffebccfe40f243859f1c766bc118f16 Mon Sep 17 00:00:00 2001 From: LHerskind Date: Fri, 22 Sep 2023 13:04:06 +0000 Subject: [PATCH] chore: tiny nit --- docs/docs/dev_docs/contracts/syntax/state_variables.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/dev_docs/contracts/syntax/state_variables.md b/docs/docs/dev_docs/contracts/syntax/state_variables.md index 3f4fc3b4d91f..830d35388240 100644 --- a/docs/docs/dev_docs/contracts/syntax/state_variables.md +++ b/docs/docs/dev_docs/contracts/syntax/state_variables.md @@ -4,7 +4,7 @@ title: State Variables State variables come in two flavours: [**public** state](#publicstatet-t_serialized_len) and [**private** state](#private-state-variables). -## `PublicState` +## `PublicState` Public state is persistent state that is _publicly visible_ to anyone in the world. @@ -12,7 +12,7 @@ For developers coming from other blockchain ecosystems (such as Ethereum), this Aztec public state follows an account-based model. That is, each state occupies a leaf in an account-based merkle tree: the public state tree. See [here](/concepts/advanced/data_structures/trees#public-state-tree) for more of the technical details. -The `PublicState` struct serves as a wrapper around conventional Noir types `T`, allowing these types to be written to and read from the public state tree. +The `PublicState` struct serves as a wrapper around conventional Noir types `T`, allowing these types to be written to and read from the public state tree. ### `::new`