Original text:
Welcome message at the same time, by taking the following steps: Construct an initial Commit object with the "proposals" field <del> populated from Proposals received during the current epoch, and empty "key_package" and "path" fields. </del>  Generate a provisional GroupContext object by applying the proposals referenced in the initial Commit object, as described in above), then it MUST be populated.  Otherwise, the sender MAY omit the "path" field at its discretion. <del> If populating the "path" field: Create a UpdatePath using the new </del>  tree.  Any new member (from an add proposal) MUST be exluded from the resolution during the computation of the UpdatePath.  The GroupContext for this operation uses the "group_id", "epoch", "tree_hash", and "confirmed_transcript_hash" values in the initial <del> GroupContext object. </del>  Assign this UpdatePath to the "path" field in the Commit. Commit to the null optional.  Define "commit_secret" as the all- zero vector of the same length as a "path_secret" value would be. <del> Generate a new KeyPackage for the Committer's own leaf, with a "parent_hash" extension.  Store it in the ratchet tree and assign it to the "key_package" field in the Commit object. </del> If one or more PreSharedKey proposals are part of the commit, derive the "psk_secret" as specified in pre-shared-keys, where the order of PSKs in the derivation corresponds to the order of ratchet tree and generate the "commit_secret": Apply the UpdatePath to the tree, as described in <del> synchronizing-views-of-the-tree, and store "key_package" at the Committer's leaf. </del>  Verify that the KeyPackage has a "parent_hash" extension and that its value matches the new parent of the sender's leaf

Reviewer comments:
It looks like in Commit was moved to in UpdatePath, but some docs didn't get updated.

Revised text:
Welcome message at the same time, by taking the following steps: Construct an initial Commit object with the "proposals" field  <ins> populated from Proposals received during the current epoch, and an empty "path" field. </ins> Generate a provisional GroupContext object by applying the proposals referenced in the initial Commit object, as described in above), then it MUST be populated.  Otherwise, the sender MAY omit the "path" field at its discretion.  <ins> If populating the "path" field: Create an UpdatePath using the new </ins> tree.  Any new member (from an add proposal) MUST be exluded from the resolution during the computation of the UpdatePath.  The GroupContext for this operation uses the "group_id", "epoch", "tree_hash", and "confirmed_transcript_hash" values in the initial  <ins> GroupContext object.  The "leaf_key_package" for this UpdatePath must have a "parent_hash" extension. </ins> Assign this UpdatePath to the "path" field in the Commit. Commit to the null optional.  Define "commit_secret" as the all- zero vector of the same length as a "path_secret" value would be.  If one or more PreSharedKey proposals are part of the commit, derive the "psk_secret" as specified in pre-shared-keys, where the order of PSKs in the derivation corresponds to the order of ratchet tree and generate the "commit_secret": Apply the UpdatePath to the tree, as described in  <ins> synchronizing-views-of-the-tree, and store "leaf_key_package" at the Committer's leaf. </ins> Verify that the KeyPackage has a "parent_hash" extension and that its value matches the new parent of the sender's leaf