Splunk® Style Guide

Splunk Style Guide

Acrobat logo Download manual as PDF

Acrobat logo Download topic as PDF


Don't use common abbreviations, such as a.k.a., e.g., etc., and i.e., in documentation and UI text. Instead, use precise language and state what you mean. See the Usage dictionary for terms to use instead of abbreviations.

For keyboard shortcuts, abbreviate the names of keys only if you have a space constraint. See Keyboard shortcuts.

It's okay to abbreviate a unit of measurement in text. See Measurements.

Last modified on 28 April, 2023
Line breaks
Acronyms and initialisms

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

Was this documentation topic helpful?

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