fixup! Add EEP for native records

Apply Rickard's suggestions.

Author: bjorng

eeps/eep-0079.md

@@ -48,7 +48,7 @@ loop(State) ->
     {get_avg, From} ->
       From ! State#state.avg, loop();
     {get_values, From} ->
-      From ! State#state.avg, loop(State#state{values = [], avg = 0.0});
+      From ! State#state.values, loop(State#state{values = [], avg = 0.0});
     {put_value, Value} ->
       Values = [Value | State#state.values],
       loop(State#state{values = Values, avg = lists:sum(Values) / length(Values)})
@@ -59,8 +59,8 @@ Goals
 =====
 
 1. Replace most tuple-record usages without having to update anything
-but the declaration.  This includes all of the record syntax (create,
-read, update, match, key index).
+but the declaration. This includes the major parts of the classic
+record syntax (creating, reading, updating, and matching).
 
 2. Create something that is useful in building both APIs and keeping
 internal state (efficient).
@@ -79,7 +79,7 @@ The following items will never be considered as goals.
 5. Supporting `element/2` for native records.
 6. Supporting opaque records.
 7. Having `undefined` as default when neither the record definition nor
-   the record creation provides a value a field.
+   the record creation provides a value for the field.
 8. `_` wildcard default for assigning a value to any field not explictly
    initialized.
 
@@ -329,8 +329,8 @@ native-record definition is **not** consulted.
 
 An access operation fails with a `{badrecord,Expr}` error if:
 
-* When the native-record value was created, the definition of the
-  record was not exported, and it is now used outside its definining
+* The definition of the record was not exported when the native-record
+  value was created, and it is now used outside its definining
   module.
 
 * `Expr` does not evaluate to a native-record value of the expected
@@ -356,9 +356,8 @@ This access operation fails with a `{badfield,Field}` error if:
 
 * The field `Field` is not defined in the native-record value.
 
-* When the native-record value was created, the definition of the
-  record was not exported, and it is now used outside its definining
-  module.
+* The definition of the record was not exported when the native-record
+  value was created, and it is now used outside its defining module.
 
 ### Updating native records
 
@@ -376,9 +375,8 @@ definition is **not** consulted.
 
 An update operation fails with a `{badrecord,Expr}` error if:
 
-* When the native-record value was created, the definition of the
-  record was not exported, and it is now used outside its definining
-  module.
+* The definition of the record was not exported when the native-record
+  value was created, and it is now used outside its defining module.
 
 An update operation fails with a `{badfield,FN}` error if:
 
@@ -389,17 +387,17 @@ Native-record update expressions are not allowed in guards.
 
 ### Anonymous update of native records
 
-The following syntax allows update any record having the given fields:
+The following syntax allows updating any record that has the given
+fields:
 
 ```erlang
 Expr#_{Field1=Expr1, ..., FieldN=ExprN}
 ```
 
 An update operation fails with a `{badrecord,Expr}` error if:
 
-* When the native-record value was created, the definition of the
-  record was not exported, and it is now used outside its definining
-  module.
+* The definition of the record was not exported when the native-record
+  value was created, and it is now used outside its defining module.
 
 * `Expr` does not evaluate to a native-record value of the expected
   type `#Name` or `#Module:Name` (that is, it is either not a native
@@ -429,9 +427,8 @@ When a native-record value is matched, its native-record definition is
 
 Pattern matching fails if:
 
-* When the native-record value was created, the definition of the
-  record was not exported, and it is now used outside its definining
-  module.
+* The definition of the record was not exported when the native-record
+  value was created, and it is now used outside its defining module.
 
 * The pattern references a FieldK and the native-record value does not
   contain this field.
@@ -487,7 +484,7 @@ TODO: What should the name of that BIF be?
 
 ### Fetching field index
 
-Fetching the record index using the `Rec#name.field` syntax is not
+Fetching the record index using the `#name.field` syntax is not
 supported, because there is no way it can actually be used, since neither
 ETS nor `element/2` will work with native records.
 
@@ -574,11 +571,11 @@ is_user(U) -> is_record(U, user).
 
 ### Native records in specs and in the language of types
 
-Native records that can be used as types using the following syntax:
+Native records can be used as types using the following syntax:
 
 ```erlang
 %% local or imported native-record
-#RecordName{TField :: TType, ... }
+#RecordName(TField :: TType, ... )
 %% remote native-record
 #Module:RecordName(TVar1, ..., TVarN)
 ```
@@ -624,7 +621,7 @@ Native records can be documented just as functions/types/callbacks can be docume
 If you export a record it will be visible and you have to add `-doc false.`
 for it to not be shown.
 
-If in a spec, type, callback, or native record refers to an undocumented
+If a spec, type, callback, or native record refers to an undocumented
 local native record, the compiler will issue a warning.
 
 ### Compatibility between OTP 28 and OTP 29
@@ -653,10 +650,9 @@ number()
 ```
 
 Native-record values are ordered by their fully qualified name, then
-by their visibility, then their keys, and finally by field values
-(field values are considered as maps). Equality is defined through
-equality of all the properties: names, visibility, keys and field
-values.
+by their visibility, then by their keys, and finally by field values.
+Equality is defined through equality of all the properties: name,
+visibility, keys, and field values.
 
 ### Reflection