Merge pull request #284 from lf-lang/typo-state-var

Fixing typos in explanation of State Declaration.
lf-lang · Sep 11, 2024 · 5aef94e · 5aef94e
2 parents ea0b763 + 4608cc0
commit 5aef94e
Show file tree

Hide file tree

Showing 5 changed files with 5 additions and 5 deletions.
diff --git a/docs/writing-reactors/parameters-and-state-variables.mdx b/docs/writing-reactors/parameters-and-state-variables.mdx
@@ -104,7 +104,7 @@ A reactor declares a state variable as follows:
 </ShowIf>
 </ShowIfs>
 
-The type can any of the same forms as for a parameter.
+The type can be any of the same forms as for a parameter.
 
 The `<value>` is an initial value and, like parameter values, can be given as an [expression](../reference/expressions.mdx) or target language code with delimiters `{= ... =}`. The initial value can also be given as a parameter name. The value can be accessed and modified in a target-language-dependent way as illustrated by the following example:
 

diff --git a/versioned_docs/version-0.5.0/writing-reactors/parameters-and-state-variables.mdx b/versioned_docs/version-0.5.0/writing-reactors/parameters-and-state-variables.mdx
@@ -104,7 +104,7 @@ A reactor declares a state variable as follows:
 </ShowIf>
 </ShowIfs>
 
-The type can any of the same forms as for a parameter.
+The type can be any of the same forms as for a parameter.
 
 The `<value>` is an initial value and, like parameter values, can be given as an [expression](../reference/expressions.mdx) or target language code with delimiters `{= ... =}`. The initial value can also be given as a parameter name. The value can be accessed and modified in a target-language-dependent way as illustrated by the following example:
 

diff --git a/versioned_docs/version-0.6.0/writing-reactors/parameters-and-state-variables.mdx b/versioned_docs/version-0.6.0/writing-reactors/parameters-and-state-variables.mdx
@@ -104,7 +104,7 @@ A reactor declares a state variable as follows:
 </ShowIf>
 </ShowIfs>
 
-The type can any of the same forms as for a parameter.
+The type can be any of the same forms as for a parameter.
 
 The `<value>` is an initial value and, like parameter values, can be given as an [expression](../reference/expressions.mdx) or target language code with delimiters `{= ... =}`. The initial value can also be given as a parameter name. The value can be accessed and modified in a target-language-dependent way as illustrated by the following example:
 

diff --git a/versioned_docs/version-0.7.0/writing-reactors/parameters-and-state-variables.mdx b/versioned_docs/version-0.7.0/writing-reactors/parameters-and-state-variables.mdx
@@ -104,7 +104,7 @@ A reactor declares a state variable as follows:
 </ShowIf>
 </ShowIfs>
 
-The type can any of the same forms as for a parameter.
+The type can be any of the same forms as for a parameter.
 
 The `<value>` is an initial value and, like parameter values, can be given as an [expression](../reference/expressions.mdx) or target language code with delimiters `{= ... =}`. The initial value can also be given as a parameter name. The value can be accessed and modified in a target-language-dependent way as illustrated by the following example:
 

diff --git a/versioned_docs/version-0.8.0/writing-reactors/parameters-and-state-variables.mdx b/versioned_docs/version-0.8.0/writing-reactors/parameters-and-state-variables.mdx
@@ -104,7 +104,7 @@ A reactor declares a state variable as follows:
 </ShowIf>
 </ShowIfs>
 
-The type can any of the same forms as for a parameter.
+The type can be any of the same forms as for a parameter.
 
 The `<value>` is an initial value and, like parameter values, can be given as an [expression](../reference/expressions.mdx) or target language code with delimiters `{= ... =}`. The initial value can also be given as a parameter name. The value can be accessed and modified in a target-language-dependent way as illustrated by the following example: