However, we actually used a (0,2,1) topology, to allow features that also look at the "upcoming" input phoneme that immediately follows the edit's input (/@/ in Figure 2).
for each natural class, we also included contextual versions of each EDIT or BIGRAM feature, which fired only if the "upcoming" input phoneme fell in that natural class.