Wording: call schedule "schedule" again

Here's a screenshot of Apple Reminders: - the smart folder for scheduled tasks is called "scheduled" - the command to schedule a task for tomorrow is *not* in the same block as "Mark as Completed" but visually *separated* by lines and other commands - the wording "Due Tomorrow" is concise, but it wouldn't translate to Noteplan. There are no due dates in Noteplan (yet). In Noteplan I would still prefer "Schedule for Tomorrow".

Here is an example, how the verb *to schedule for* is used in real life by a real Noteplan user. Stacey Roshan says "you can schedule things for another day" at 7:48 in her [video](https://www.youtube.com/watch?v=qd4MiV2h9LA) *How I'm Using NotePlan 3 to Organize My Day, Meeting Notes, Reminders, My Daily Template, and More*. At 8:40 she says, referring to the same command: "I could schedule [the selected tasks]".

Here are some examples of the user interface that already have the requested wording. - Menu *Format > Mark as Scheduled* - Menu *Note > Schedule All Open Tasks* - *Preferences > To Do* - Editing a filter for Review All screenshots NP 3.0.19 (617)

I'm planning to change it so that you have all options: add just a link, copy & paste, and cut & paste

Here's another example. I learned only recently in an [old blog post](https://www.noteplan.co/blog/update-multiple-todo-selection-…), that it is possible to schedule several tasks at once. Nice! But why didn't I discover this useful feature in the app itself? Because there is no "schedule" command. I noticed only commands called "Move Task To". The singular implied, at least in my ears, that only one task can be moved at at time. I wasn't aware that this command triggers a much more interesting behavior: - It can be used for more than one task at a time. - It does not move/copy *all* tasks, but only *open* tasks. - And it copies not just tasks, but also headings. The functionality is great, but the wording is misleading. I'd prefer these commands to be called "Schedule for". Then I wouldn't be disappointed, that this command doesn't actually "move" a task. On the contrary, I would expect complex behavior that depends on the selected items, their context and my preference settings. BTW, I wouldn't mind an additional menu item with a generic "Schedule Task(s) …" command.

Some good analysis here. (Personally I have scripts that do actually *move* items marked `>date` between notes as I find that cleaner.)

Here is an example how the original wording in NP1 makes more sense than the current wording in NP3. The current menu item "Mark as Moved" is a contradiction in itself. When I look up "to move" in [a dictionary](https://www.merriam-webster.com/dictionary/move), I read "to transfer (something, such as a piece in chess) from one position to another". Only a task that was *not* transferred to another position, can be *marked* in its original position. Call the menu item "Schedule …" or "Schedule for …" and everything makes sense again. Scheduling is a complex action with many options. Who knows in advance, which option the user will pick? Marking the original task with `- [>]` is just *one of many* possible outcomes. "Schedule for …" is perfectly compatible with Apple's [Human Interface Guidelines](https://developer.apple.com/design/human-interface-guideline…) ("Describe the action that occurs when the menu item is chosen"). It's perfectly compatible with the [dictionary definition](https://www.merriam-webster.com/dictionary/schedule) of *to schedule*: "to appoint, assign, or designate for a fixed time". This is just a change of wording. The functionality is still the same!