fixed the double successor fringe use case by updating the double predecessor's double successor with our own information