chore: tiny nit

AztecProtocol · Sep 22, 2023 · 7fd191b · 7fd191b
1 parent 66ce38f
commit 7fd191b
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docs/docs/dev_docs/contracts/syntax/state_variables.md b/docs/docs/dev_docs/contracts/syntax/state_variables.md
@@ -4,15 +4,15 @@ title: State Variables
 
 State variables come in two flavours: [**public** state](#publicstatet-t_serialized_len) and [**private** state](#private-state-variables).
 
-## `PublicState<T, T_serializeD_LEN>`
+## `PublicState<T, T_SERIALIZED_LEN>`
 
 Public state is persistent state that is _publicly visible_ to anyone in the world.
 
 For developers coming from other blockchain ecosystems (such as Ethereum), this will be a familiar concept, because there, _all_ state is _publicly visible_.
 
 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<T, T_serializeD_LEN>` 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<T, T_SERIALIZED_LEN>` 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`