Fixing Multi-Threaded Code Order

Phase2 Technology's publishing platform lets editors queue a batch of content edits that must be applied to the CMS in the exact sequence editors submitted them, even though the rendering step for each edit is slow enough that it runs concurrently. A teammate's first draft of the apply step is below, and in staging the published order sometimes comes out scrambled.

package publisher

import "fmt"
import "sync"

type Edit struct {
	SequenceID int
	Payload    string
}

func ApplyEdits(edits []Edit) []string {
	var wg sync.WaitGroup
	var applied []string

	for _, edit := range edits {
		go func() {
			wg.Add(1)
			defer wg.Done()
			result := renderEdit(edit)
			applied = append(applied, result)
		}()
	}

	wg.Wait()
	return applied
}

func renderEdit(edit Edit) string {
	return fmt.Sprintf("seq=%d payload=%s", edit.SequenceID, edit.Payload)
}

Analyze this code and explain how you would change it so the rendering still happens concurrently but the edits are always applied to the CMS in the order editors submitted them (SequenceID).