So, iOS will often autocorrect a mis-typing of "in a" to "Ina", because OF COURSE many more people have a friend with Scandinavian ancestry that they're referring to to a third party via text than would EVER need to type "in a".
So, fine, fucking thing overwrites my error with its own, now it says "Ina" in the middle of a sentence.
delete-delete-delete-delete and type "in a" where it should have been to begin with.
iOS writes "In a", capitalizing the "in" even though that's absolutely senseless in this context.
So you have to delete everything AGAIN, UNCHECK the shift key that will otherwise needlessly capitalize your "in", and then type "in a" for what is now the sixteenth time.
What the fuck, iOS? Wouldn't a better assumption be that, since the capitalization only originated with your erroneous autocorrection to begin with, and given that the writer is now deleting your autocorrection, indicating that it was WRONG, that your capitalization was ALSO incorrect and therefore you should leave the goddamned keyboard in its default state instead of invoking a special mode that, in every other instance, has to be specifically invoked by the user?
God DAMN it. This happens to me a million times a day. I know it's because Apple (and Android does this too) expects you to choose from their row above the keyboard of possible corrections rather than just do the work yourself, but I can retype this shit faster than I can move my thumbs up to that row and choose as the cognitive workload is higher (and therefore slower) to do that than to rely on the built-in muscle memory for a retype. I have where each normal keyboard key is memorized; one can NOT, by definition, memorize where keys that pop up only due to specific context will be, so fuck that row of choices.
I further know that most people give two shits about capitalization or grammar or spelling at all these days, and most texts are written in a combination of emoji and whatever letters pop up when some Vine-addled fuckboi just drags his dick across the Apple keyboard, but I'm going to be back over here raging against the dying of the light on this one, however much Apple insists on fighting me about it.