Source: https://developers.google.com/style/tense ↗\n\n# Present tense

  Stay organized with collections



  Save and categorize content based on your preferences.\n\n- Home\n- Products\n- Style\n\nUse present tense for statements that describe general behavior that's not associated with

a particular time.\n\nRecommended: Send a query to the service. The server sends an acknowledgment.\n\nNot recommended: Send a query to the service. The server will send an acknowledgment.\n\nHowever, it’s fine to use future tense (will) to distinguish an action that will occur in the future.\n\nRecommended: Add the filename to the backup list. The file will be archived the next time the backup process runs.\n\nIn the following example, future tense is appropriate because Pub/Sub sends messages asynchronously; messages are not received immediately by subscribers.\n\nRecommended: A message is sent that will notify any Pub/Sub subscribers.\n\nNot recommended: A message is sent that notifies any Pub/Sub subscribers.\n\nDon’t use future tense to describe how a product or feature will work after the next release or update. For more information, see Document future features.

Also avoid the hypothetical future would—for example: Recommended: If you send an unsubscribe message, the server removes you from the mailing list. Not recommended: You can send an unsubscribe message. The server would then remove you from the mailing list.\n\nAlso avoid the hypothetical future would—for example:\n\nRecommended: If you send an unsubscribe message, the server removes you from the mailing list.\n\nNot recommended: You can send an unsubscribe message. The server would then remove you from the mailing list.\n