According to amplitude academy, fundamentals of data taxonomy design course, they recommend using past tense verb. (see the bold & underlined text)

Here are some best practices for creating a taxonomy that makes your data easy to learn:

• Maintain a consistent style (i.e. case and punctuation) for all of your events and properties. For example, you may use Title Case for all events and snake_case for all properties. Regardless of what you choose, the most important thing is to stay consistent. For easy differentiation, you should try using one style for your events and a different one for your properties.
• For events, maintain a consistent syntax that includes a noun and a verb. For example, all of your events may follow noun + verb or verb + noun order. This will help you and other data users better map what event is triggered when an action is done in the product.
• Name properties such that you can intuit their data type. While this may not always be possible, consider naming your properties so someone can figure out what the data type of that property value might be. For example, a property that takes boolean values could be named is_subscriber; a property that acts as a counter could be named num_purchases. While this is helpful, optimize for readability first.
• Maintain the same verb tense across all events. We recommend using past tense to indicate that the event is triggered once the action is completed. For example, Category Browsed would be preferred over Category Browse. More importantly, do not mix tenses or people might be confused about when the event gets triggered.
• Be concise in your naming. The more concise you can make your events and properties, the easier the query will be for others to read and comprehend. Since longer event and property names may be cut off at first glance, always consider how you can make an event name two words instead of five. Balance this with using the real-world language of the customer; this will make searching for events and creating new charts far more intuitive for new data users.

But, according to Data taxonomy playbook, they recommend using present tense verb.

Consistency in naming means that all events share the same syntax. If you do not have your own standard syntax in naming data, we recommend (1) all lowercase—this removes the possibility of casing instrumentation errors, and (2) present-tense verbs—this minimizes any confusion. Regardless of the syntax you choose, the most important factor is that all events consistently follow your chosen syntax.

I understand that tense is not that important(the most important thing is easy to understand and clear event name) but which is better?