More intuitive workflow step names

[alyssadai]

"Categorization" and "Annotation" may not be the most intuitive names for the stages in the annotation tool.

One alternative could be "Column mapping" and "Value mapping", or "Column annotation" and "Value annotation".

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
  apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
  label in the future. Use sparingly!

[Manya-tech]

Hello,

I am Manya Gupta. I was using the annotation tool as a potential GSOC contributor and I agree with your suggested changes. The suggested alternatives do sound more intuitive for a beginner in data annotation like me.
Also, I noticed that the names in the navbar are in lowercase while that's not the case in the images provided in the user guide. I also discovered some grammatical errors and would like to fix them.

Thank you.

[rmanaem]

Hi @Manya-tech
Thanks for the feedback.
Glad to hear you're interested in contributing. Please open an issue for the fixes you'd like to implement and let us know that you'd like to address them there.

[Manya-tech]

Hi @rmanaem

Sure! I will open an issue and mention everything there.

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
  apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
  label in the future. Use sparingly!