fixup up rust init

Author: soc

_languages/rust-struct-initializer-mistake.md

@@ -103,7 +103,7 @@ fn main() {
 }
 ```
 
-##### How to Distinguish between a variable assigment and a named parameter use inside a function invocation?
+#### How to Distinguish between a variable assigment and a named parameter use inside a function invocation?
 
 Example:
 
@@ -117,11 +117,11 @@ Two points have to be considered here:
   - Frequency: Are variable assignments within function calls or function calls with named parameters projected to be used more often?
   - Intuitivity: How can the syntax be distributed to those two use-cases such that the configuration makes sense from a user point-of-view?
 2. Reducing the harm from mix-ups:
-  - Can code that looks correct behave unexpectedly
+  - Can code that looks correct be interpreted unexpectedly? I. e.
 
 In general, there are multiple options:
 
-###### Try to use the same syntax for both variable assigments and named parameters
+##### Try to use the same syntax for both variable assigments and named parameters
 
 This means that named parameters simply act like another scope in which identifiers are looked up.
 
@@ -134,7 +134,7 @@ The danger with this approach is that changing the name of a named parameter can
 
 It also means that variables with the same name as a parameter name cannot be assigned within a function call.
 
-###### Let variable assignments use the "good" syntax and give named parameters some workaround syntax
+##### Let variable assignments use the "good" syntax and give named parameters some workaround syntax
 
 In this example, the orkaround syntax for named parameters is a `.` prefixed to the parameter name.
 
@@ -148,8 +148,7 @@ In this example, the orkaround syntax for named parameters is a `.` prefixed to
     someFunction(.a = 23)
 
 
-
-###### Let named parameters use the "good" syntax and give variable assignments some workaround syntax
+##### Let named parameters use the "good" syntax and give variable assignments some workaround syntax
 
 Inside a functions argument list, the first level of `=` use is always a named parameter and never a
 variable assignment, even if some variable `a` would be in scope.[^2]