Avoid unnoticed carb entries about loop

[marionbarker]

I don’t mean to minimize that this was frightening. But this is the design and it is documented. The Button you pressed says Save and Bolus. Perhaps we should modify the button to say Save Carbs and Bolus. Would that have made it more likely you would have taken a different action?

I certainly will move the warning box in this section to be higher up. And I will ask for more review from mentors (and you) on better words to get this concept across to new Loopers.

https://loopkit.github.io/loopdocs/operation/features/carbs/#meal-entry_1

[oliverstory]

Maybe 'Save carbs and attempt bolus' would be a good label for the button? Although it is a bit long.

Or 'Save carbs then bolus' - shorter but clear that the 'save carbs' happens first, so if you then get a 'bolus failed' message it is clearer that it's the bolus part rather than the 'save carbs' part that failed.

Our little looper is at daycare and I have received several calls from staff members who've encountered an issue at this step and wondered what to do next. I've seen this occur both with the 'pod not connected' error and when there's an automatic bolus in progress when you press 'save and bolus'.