clarifying keeping message for #2

Simple text changes, let me know if for the `replaceAll` logic branch if we should indicate that it is a forced replace replace as `no conflict` is sorta misleading in that context.
Sorry whoops, didn't notice the two blocks were different.  Personally if there's no file i wouldn't mind silence.  If gulp-conflict isn't asking me what to do with a conflict, I don't think it needs to speak up at all.

But that's just me.  "Creating" might be a better term here, unless I'm misunderstanding what the situation is in this block.