Source: https://developers.google.com/style/excessive-claims\n\n# Avoid excessive claims
Stay organized with collections
Save and categorize content based on your preferences.\n\n- Home\n- Products\n- Style\n\n\n## Page Summary\n\n- Avoid excessive claims in documentation, which are statements about performance, cost, or security that aren't easily verifiable or could be invalidated by future events.\n- Refrain from using superlatives and subjective language when describing products and features, instead focusing on factual and objective information.\n- When making specific performance or security claims, ensure they are backed by verifiable data and consider potential future scenarios that could impact their validity.\n- Emphasize the intended benefits and design of features rather than making absolute guarantees, especially regarding security.\n- Prioritize writing factually and objectively, providing verifiable information that will remain true throughout the documentation's lifespan, even when comparing products.\n\nAvoid excessive claims in documentation, which are statements about performance, cost, or security that aren't easily verifiable or could be invalidated by future events.\n\nRefrain from using superlatives and subjective language when describing products and features, instead focusing on factual and objective information.\n\nWhen making specific performance or security claims, ensure they are backed by verifiable data and consider potential future scenarios that could impact their validity.\n\nEmphasize the intended benefits and design of features rather than making absolute guarantees, especially regarding security.\n\nPrioritize writing factually and objectively, providing verifiable information that will remain true throughout the documentation's lifespan, even when comparing products.\n\nIn documentation, don't make excessive claims. An excessive claim is an assertion
in the documentation that does any of the following:\n\n- Makes a statement about performance or cost that isn't easily verifiable with data
that's available to the reader.\n- Makes a statement about security that would be invalidated by a security incident.\n- Makes a statement that might be interpreted as subjective or even disparaging,
especially about third-party products.\n\nWhen you're assessing whether some text makes an excessive claim, take into account
not just what's true today about a product's performance, cost, security, or
functionality, but what might be true in the future.\n\nConsider the following guidelines:\n\n- When you describe products, avoid superlatives like best, simplest,
fastest, never, and always. Similarly, be
careful about words like ensure and guarantee and use them only when
something can truly be ensured or guaranteed.\n- If you make specific performance claims—how fast a product is, how much storage
it requires, and so on—make sure that you reference the source of your information.\n- If documentation claims that a product is secure, the documentation
is invalid (and not credible) if someone succeeds in compromising the product.
It's safer to suggest that a feature "helps with security" or "is designed for
security" because those statements are true even if a security incident occurs.\n- A statement that you make about a competitive product might be untrue if you
misinterpret how the product works, or later if the other company comes out with
a new release.\n\nThe safest approach is always to write factually and objectively, limiting what you say to
verifiable information that will be true over the lifespan of your documentation.\n\nRecommended: Our product
distributes datasets and computation in memory across a cluster, and
therefore it can be faster for this scenario than ExampleCorporation's product. For
more information, see Performance comparison.\n\nNot recommended: Our product is
faster than ExampleCorp's product.\n\nRecommended: Using our security product
is part of an overall strategy that helps prevent account takeovers from phishing attacks.\n\nNot recommended: Our security product
prevents account takeovers from phishing attacks.\n