Splunk® Style Guide

Splunk Style Guide

The guidelines in the Splunk Style Guide establish best practices for writing technical documentation. Search docs.splunk.com to find documentation related to Splunk products.

Possessive names and terms

Don't use an apostrophe to make product names, company names, or trademarked terms possessive. The following table shows some examples of what to do and not do:

Do this Don't do this
The dashboard shows data pulled from the Splunk Enterprise internal log files. The dashboard shows data pulled from Splunk Enterprise's internal log files.
Submit a case using the Splunk Support Portal. Submit a case using Splunk's Support Portal.
The search function has robust capabilities. Search's capabilities are robust.

For acceptable uses of apostrophes, see Apostrophe.

Last modified on 04 April, 2024
Plurals in parentheses   Prepositions

This documentation applies to the following versions of Splunk® Style Guide: current

Was this topic useful?

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters