If you try to rename a file to a name that’s already in use, EagleFiler adds “-1” (or “-2”, etc.) in order to make the new name unique.
Presumably that happened because you already had a file or folder named “Software” (or “software” since the Mac filesystem is case-insensitive by default).
I feel sure I have had this happen where there isn’t a same name within the same parent. But I haven’t kept any examples. If it happens again, I’ll look more closely
Currently there is a bug where if you rename the file to a new name that differs only in case, it will add -1 even though it isn’t necessary. That will be addressed in the next release.