Splunk® Style Guide

Splunk Style Guide

Acrobat logo Download manual as PDF

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.
Acrobat logo Download topic as PDF


When writing about numbers that appear in a Splunk product UI, duplicate them exactly as the UI displays. Otherwise, follow these guidelines.

Generic fractions

If you're referring to a generic fraction and not one that refers back to a specific number, hyphenate the spelled-out fraction.

Review the following table for an example of a correctly formatted generic fraction:

Do this Don't do this
The system parsed two-thirds of the events. The system parsed 2/3rds of the events.

The system parsed 2/3 of the events.

Numerical fractions

Use numerals and forward slashes with no additional formatting to represent numerical fractions. Add a space and remove the hyphen between a whole number and fraction.

Review the following table for examples of correctly formatted numerical fractions:

Do this Don't do this
1/2 ½
3/4 ¾
70 1/2 70½


Last modified on 11 January, 2024
Commas and decimals

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