In our scrum team, we can often get user stories which are not very complex and not ambiguous but have a high amount of leg work associated.
Example: We receive a user story to replace the name of a client on 100+ pages. A lot of manual work is required for this but the process of finding the content and updating is very straightforward but requires a good amount of time to complete, say 6 hours.
Because the complexity and ambiguity of the task are low we estimate it as low, but the cost of time is still a factor and effectively a day of work has been taken out.
I'm trying to rationalize in my mind how this would still work when it comes to the velocity at the end of the sprint, reasonably this could cause a reduction in velocity due to the low estimation but no less work would have been completed.
Is there a better way to handle these sorts of stories?