Merge pull request #323 from consentsam/consentsam-patch-1

Consentsam patch 1

docs/language_concepts/07_mutability.md

@@ -79,7 +79,7 @@ fn main(runtime_var: Field) -> pub Field {
 }
 ```
 
-As `runtime_var`` is a argument to the circuit it cannot be known at compile time and so assigning it to a comptime variable should fail. A circuit's arguments is the only way in which non-comptime variables can enter the circuit (excluding [brillig](./unconstrained) foreign calls).
+As `runtime_var` is a argument to the circuit it cannot be known at compile time and so assigning it to a comptime variable should fail. A circuit's arguments is the only way in which non-comptime variables can enter the circuit (excluding [brillig](./unconstrained) foreign calls).
 
 ## Globals
 

docs/language_concepts/09_distinct.md

@@ -8,7 +8,7 @@ that the witnesses being returned as public inputs are all unique.
 The `distinct` keyword is only used for return values on program entry points (usually the `main()`
 function).
 
-When using `disctinct` and `pub` simultaneously, `distinct` comes first. See the example below.
+When using `distinct` and `pub` simultaneously, `distinct` comes first. See the example below.
 
 You can read more about the problem this solves
 [here](https://github.com/noir-lang/noir/issues/1183).

docs/standard_library/cryptographic_primitives/04_ec_primitives.md

@@ -30,7 +30,7 @@ mixed coordinate representation is employed).
 ### Points
 
 (`std::ec::{tecurve,montcurve,swcurve}::{affine,curvegroup}::Point`), i.e. points lying on the
-elliptic curve. For a curve configuration `c` and a point `p`, it may be checked checked that `p`
+elliptic curve. For a curve configuration `c` and a point `p`, it may be checked that `p`
 does indeed lie on `c` by calling `c.contains(p1)`.
 
 ## Methods

versioned_docs/version-0.9.0/language_concepts/07_mutability.md

@@ -79,7 +79,7 @@ fn main(runtime_var: Field) -> pub Field {
 }
 ```
 
-As `runtime_var`` is a argument to the circuit it cannot be known at compile time and so assigning it to a comptime variable should fail. A circuit's arguments is the only way in which non-comptime variables can enter the circuit (excluding [brillig](./unconstrained) foreign calls).
+As `runtime_var` is a argument to the circuit it cannot be known at compile time and so assigning it to a comptime variable should fail. A circuit's arguments is the only way in which non-comptime variables can enter the circuit (excluding [brillig](./unconstrained) foreign calls).
 
 ## Globals
 

versioned_docs/version-0.9.0/language_concepts/09_distinct.md

@@ -8,7 +8,7 @@ that the witnesses being returned as public inputs are all unique.
 The `distinct` keyword is only used for return values on program entry points (usually the `main()`
 function).
 
-When using `disctinct` and `pub` simultaneously, `distinct` comes first. See the example below.
+When using `distinct` and `pub` simultaneously, `distinct` comes first. See the example below.
 
 You can read more about the problem this solves
 [here](https://github.com/noir-lang/noir/issues/1183).

versioned_docs/version-0.9.0/standard_library/cryptographic_primitives/04_ec_primitives.md

@@ -30,7 +30,7 @@ mixed coordinate representation is employed).
 ### Points
 
 (`std::ec::{tecurve,montcurve,swcurve}::{affine,curvegroup}::Point`), i.e. points lying on the
-elliptic curve. For a curve configuration `c` and a point `p`, it may be checked checked that `p`
+elliptic curve. For a curve configuration `c` and a point `p`, it may be checked that `p`
 does indeed lie on `c` by calling `c.contains(p1)`.
 
 ## Methods