Usage dictionary

Use to refer to both UNIX and Linux together. If only 1 system is supported, use "UNIX" or "Linux". See *nix in the Splexicon.

Don't use. Use "atypical" or "not typical" instead.

Don't use unless referring to a specific command or system language.

Otherwise, use "force quit", "cancel", "fail", "close", "stop", "end", or another term that accurately reflects the situation.

Don't use to refer to a location in a document. Directional or visual instructions are unhelpful to visually impaired users. Use "earlier" or "previous" to refer to page elements.

For versions of software, use "higher".

Use only when referring to an unscheduled search. Otherwise, don't use Latin abbreviations or terms. See ad hoc search in the Splexicon.

Don't use any other term for a search that a user launches manually. For references not about an unscheduled search, use "if needed".

Use "add-on" when writing about a Technical Add-on, Supported Add-on, or Domain Add-on in Splunk docs. See add-on in the Splexicon.

Include a hyphen and a definite article. The plural form is "add-ons". You can write it as "the add-on" after the first instance of the full name of the add-on.

In most cases, use "admin" as an adjective to identify the role-based access control label. Use "administrator" as a noun to identify a user's job title or responsibility.

Don't capitalize either term.

Use to denote a chronological sequence of events that doesn't rely on cause and effect.

Don't use to mean "when".

Use "allow" as a verb and "allow list" as a noun. For a single item, use "allow rule" or "allow entry".

Avoid this phrase. Focus on the goals a user can achieve with their product rather than what the product lets a user do.

Write with capital letters and without periods. Use to mean between midnight and 11:59 in the morning when writing the time of day.

Don't use. Pick the word that best fits the sentence.

Use instead of "vice versa" or "vice-versa".

Don't include a hyphen.

Use to refer to an application that runs on the Splunk platform. See app in the Splexicon.

Use instead of "shows up".

Use instead of "vetted".

Use instead of "have been".

Don't use. Use "now" instead.

Don't use.

Use instead of "abnormal".

Don't include a hyphen.

Use "back end" as a noun. Use "back-end" as an adjective.

Don't use if you can find a more specific term, such as server, operating system, database, network, and the like.

Don't use. Use "back end" as a noun and "back-end" as an adjective.

Put the variable name for a directory in all capital letters regardless of the operating system. If the variable name has spaces, replace the spaces with the underscore ( _ ) character.

For *nix, precede the base directory with a dollar sign ( $ ). For Windows, surround the base directory with percent signs ( % ).

Don't use to refer to a location in a document. Directional or visual instructions are unhelpful to visually impaired users. For page elements, use "following", "later", or "next".

For versions of software, use "lower".

Don't use. Use "deny list" as a noun and "deny" as a verb. There are additional synonyms you can use in specific situations:

• "Deny" refers to access.

• "Reject" refers to validity.

• "Exclude" refers to inclusion.

For IP traffic, for example, "deny" is suitable. For files or rules, "exclude" might be more specific.

Use to describe a logical operator that takes 1 of 2 values, generally True and False.

Always capitalize.

Don't use. Use "safe", "secure", or another unambiguous term.

Use instead of "via".

Use to mean ability instead of "have the option to" or "is able to".

Use as 1 word instead of "can not".

Don't use as 2 words.

A user action within the Splunk platform. Use this term to refer to Splunk role-based access controls (RBAC). See capability in the Splexicon. Don't use to refer to the functionality or features of a product.

Don't include a hyphen when you write the term after the noun that it modifies. Include a hyphen when you write the term before the noun that it modifies.

When used to mean verify, use instead of "double-check".

You can also use "check" in the context of selecting a check box.

Use as 2 words. To describe the action of using the check box, use "check or uncheck a check box", or "select or deselect a check box".

Don't use. Use "see".

Use to mean the validated architecture of Splunk Cloud Platform. Always capitalize. Don't include the definite article and don't use "Classic" on its own. Use with the preposition "on" when describing how to use an Experience or its components. Always refer to "Experience" in the same sentence when describing the designation.

Use instead of "purge". Alternatively, use "delete" or "remove".

Don't use. Use "select". Avoid terms that are specific to certain devices and input methods.

Don't use when referring to UI selections. Use "select".

Don't include a hyphen when you write the term after the noun that it modifies. Include a hyphen when you write the term before the noun that it modifies.

Use "command line" as a noun. Use "command-line" as an adjective.

Use lowercase letters prefaced with a period ( . ) or spell out "configuration file". See configuration file in the Splexicon.

Use instead of "preconfigured".

Don't use. Use "can" or write the sentence in the imperative mood. Avoid the subjunctive mood.

Don't use Domain Add-on or the abbreviation DA when you write about the product.

It's okay to use "DA" if it's used in a file or path.

Don't use. Use "dark theme" instead.

Use lowercase letters when writing generally about the color contrast choice that a user can select for their UI. Don't use "dark mode". Follow the capitalization used in the UI.

Use as a singular mass noun. Write "data is" rather than "data are", and use "less data" rather than "fewer data". Don't use "datum".

Use "data model" when referring to a knowledge object. Use "datamodel" when used as a search command.

See data model in the Splexicon.

Use as 2 words.

Use as 1 word.

Use as 1 word. See dataset in the Splexicon.

Don't use. Use "data" instead.

Use instead of "out-of-the-box".

Use instead of "purge". Alternatively, use "clear" or "remove".

Don't use. Use "show" instead.

Use instead of "blacklist". Use "deny" as a verb and "deny list" as a noun.

Use to mean the process of setting up the components for a partial or entire system, which can include installing and configuring software and hardware. Use "install" to mean installing a piece of software.

Don't use. Use "want" instead.

Don't spell as "dialogue box". Use "dialog box" instead of "modal" or "pop-up" when referring to the UI control.

Use "dialogue" when referring to a conversation. Use "dialog box" when referring to the UI control.

Use when discussing file system structures in a CLI context or when addressing developers who work with file structures programmatically. For CLI contexts, don't use "folder", which is typically used in GUI contexts.

Don't use. Choose a plain-language alternative that describes the action or state. For example:

Don't use. Use "check" or "make sure" instead.

Use as 2 words when the emphasis is on "not". Otherwise, it's okay to use "don't".

Avoid using "domestic" to refer to the United States. Use a more specific reference, like "in the US".

Use as an adjective. For a verb, use "drag", which implies drop.

Use "drill down" as a verb. Use "drilldown" as a noun, adjective, or interactive functionality. Don't use "drill-down". See drilldown in the Splexicon.

Use as an adjective. Include a noun, such as "menu" or "list", after "drop-down".

Don't use. Use "placeholder data" instead.

Don't use to refer to versions of software. Use "lower".

It's okay to use "earlier" to refer to parts of documentation or page elements that precede a user's current location, such as "See <link to section> earlier in this topic". If appropriate, you can also use "previous".

Don't use Latin abbreviations or terms. Use "for example" instead.

Don't use. Pick the word that best fits the sentence.

Don't use to show the counteraction of turning off a feature, deactivating a feature, or describing a deactivated feature.

Choose a logical plain-language alternative that explains the action or state. For example:

• Activate, activated, activates

• Select, selected, selects

• Show, shows

• Turn on, turned on, turns on

Use instead of "re-enable".

Avoid this phrase. Focus on the goals a user can achieve with their product rather than what the product lets a user do.

Use as 1 word.

Use as a verb to refer to inputting text. Don't use "specify". Don't use "type" because there are multiple ways to enter text.

Use instead of "re-enter".

Don't use. Use "UNIX time" instead.

Don't use Latin abbreviations or terms. Be specific and concrete when you write. Use "and so on" instead.

Don't use common abbreviations in place of precise language. Use "for example" instead.

Don't use. Use "run" instead.

Use instead of "grandfathered".

Use to refer to a named Experience such as Victoria Experience or Classic Experience. Always capitalize. Don't include a definite article. Use with the preposition "on" when describing how to use an Experience or its components.

Use as 2 words when written as a verb. Use as 1 word when written as a noun or adjective.

Don't use. Use "unrecoverable" or choose another unambiguous term.

A piece of code shipped with a product that provides a tool a user can use to complete a task or action. Generally, this term is best used in release notes to describe updates to a product release. Avoid documenting features and instead put the emphasis on how a user can achieve their goal.

Don't use to refer to the capabilities or functionality of a product.

Don't use. Use "retrieve" instead.

Include a hyphen between "field" and "value" when they modify the word "pair".

Use as 2 words. Don't use "filename".

The suffix appended to a specific file. Put in lowercase letters.

A path that describes a location in a file system structure. Use as 2 words. Don't use "filepath". When writing out file paths, use a forward slash ( / ) for *nix and a backslash ( \ ) for Windows. List both the *nix and Windows file paths, in that order.

Use angle brackets to indicate parts of a file path that differ by user or operating system, such as /home/<username>/.login.

Use as 2 words. Don't use "filesystem".

Use "file type" to describe a broad file category, such as a Portable Document Format (PDF) document or Graphics Interchange Format (GIF) file. It's okay to shorten the file type as an abbreviation.

Capitalize the abbreviation when it's used as an adjective or when it stands alone in text. An exception to the standard styling for file types is for configuration files (.conf files) which are styled like a file name extension.

Don't use. Use "file name" instead.

Don't use. Use "file path" instead.

Don't use. Use "file system" instead.

Don't use. Use "top-level entity" instead.

Don't use terminology that assumes race to describe color. Use the most accurate word to describe the color.

Use when referring to file system structures in a GUI context. For GUI contexts, don't use "directory", which is typically used in CLI contexts.

Use to refer to parts of documentation or page elements that immediately come after a user's current location, such as "in the following section" or "in the following table".

If appropriate, you can also use "later" and "next".

Use instead of "e.g.", "ex.", or "for instance".

Don't use. Use "for example" instead.

Avoid "foreign" when referring to a location outside the United States. Use a more specific reference, like "outside the US".

Use instead of "hangs".

Use "front end" when written as a noun. Use "front-end" when written as an adjective. Don't use if you can find a more specific term, such as the name of the product, feature, app, and the like.

Use this term to describe how Splunk product features work. Don't use to refer to the capabilities or features of a product.

Don't use. Use "exempt" instead.

Use instead of "wizard" when you must refer to the general component. Always aim to describe the user's actions and goals instead of the components and features of the product.

Use "wizard" only if you need to refer to a UI component label containing the word "wizard".

Don't use. Use "stops responding" or "freezes" instead.

Use only for a technical or developer audience when referring to coding values and functions directly into the source code rather than obtaining values from general input or external sources.

Include a hyphen in all uses of the term.

Use instead of "needle-in-a-haystack".

Don't use. Use "are" instead.

Don't use. Use "know" instead.

Don't use. Use "can" instead.

Don't use in documentation. Use "they", "them", their", "a user", "the users", or another inclusive term.

Don't use. Use "hexadecimal" instead.

Use instead of "later" to refer to versions of software.

Don't use. Use "select", "enter", or another device-agnostic term.

Use instead of "homepage".

Use instead of "hostname".

Don't use. Use "home page" instead.

Don't use. Use "host name" instead.

Use instead of "point to" or "mouse over" to describe the action of positioning the pointer over a UI item.

Don't use. Use "stops responding" or "freezes" instead.

Don't use Latin abbreviations or terms. Use "in other words" instead.

Use to indicate a hypothetical situation, a possibility, or a condition that must be met for a particular action, behavior, or event to occur. Don't use "when" if the situation is hypothetical.

Use instead of "ad hoc".

Don't use in a task step. Use "(Optional)" to indicate the step is optional.

Don't use. Use "invalid characters" instead.

Use instead of "i.e.".

Use as a verb instead of "whitelist".

Use as a verb, not as a noun. Use to mean installing a piece of software. Use "deploy" to describe the process of setting up the components for a partial or entire system, which can include installing and configuring software and hardware.

Use to refer to a Splunk Enterprise instance. Use the full phrase "Splunk Enterprise instance" at the first use in the topic or section.

Lowercase, unless it is the first word in a sentence or part of a proper noun, such as Internet Explorer. Always use with a definite article, such as "the internet".

Use as 1 word in the context of getting data into a Splunk product.

Use instead of "illegal characters".

Don't use. Use "can" instead.

Don't use. Rewrite to make a statement about what the customer must do.

Use as a modifier, not as a standalone term. Choose the most precise noun based on the context.

Don't use.

Use only when referring to the *nix command or process. Otherwise, use "quit", "stop", or "end" based on the situation.

Include a hyphen. Don't use a slash or space. Don't use the phrase "key value" on its own.

The core section of keys on a keyboard. Special keyboard characters, such as the at symbol ( @ ), pipe ( | ), and forward slash ( / ) , aren't standardized on international keyboards.

Be explicit when referring to special keyboard characters.

Use instead of "have knowledge of".

Don't use to refer to versions of software. Use "higher".

It's okay to use "later", "following", or "next" to refer to parts of documentation or page elements that follow a user's current location, such as "See <link to section> later in this topic".

Use to refer to the latest versions of browsers and SaaS.

It's okay to use "launch" to match a UI. Otherwise, use "open" instead.

Don't use to refer to a location in a document. Use temporal language, such as "earlier", "previous", "following", "next", or "later".

Directional or visual instructions are unhelpful to visually impaired users, and locations of elements can change depending on the device being used to read the content.

Avoid this phrase. Focus on the goals a user can achieve with their product rather than what the product lets a user do.

Don't use. Use "use" instead.

Don't use. Use "light theme" instead.

Use lowercase letters when writing generally about the color contrast choice that a user can select for their UI. Follow the capitalization used in the UI when writing about a button or other component in the Splunk product UI.

Use to refer to the point where a line of text ends and a new line starts. Use as 2 words without a hyphen. Don't refer to a forced line break as a "carriage return".

Use "Linux" if only Linux is supported. Write "*nix" when referring to both Linux and UNIX.

Use "log in" as a verb. Use "log in to" to describe entering a username or password for a system. Use "log in as" to describe entering with a specific role or privileges. Don't use "log on", "sign in", or "sign on".

To use as a noun or adjective, use "login" instead.

Don't use. Use "log out" instead.

Don't use. Use "log in" instead.

Use as a verb. Don't use "log off".

Use "login" as a noun or adjective. Don't use "logon". To use as a verb, use "log in" instead.

Don't use. Use "log out" instead.

Don't use. Use "log in" instead.

If there are multiple ways a user can interact with a touch-based interface, use an input-agnostic term such as "select and hold" instead of "long press".

If you must specify the user's gesture in order to perform an action on a mobile device, you can use "long press".

Use "look up" as a verb. To use as a noun or adjective, use "lookup".

Use "lookup" as a noun, adjective, or knowledge object. To use as a verb, use "look up".

See lookup in the Splexicon.

Use to refer to versions of software. Don't use "earlier".

Use to refer to the virtual or physical machine that the instance runs on.

Use instead of "master branch".

Use instead of "double-check".

Use instead of "master".

Don't use. Use "all", "everyone", "humanity", "humankind", or another inclusive term.

Don't use. Use "manager" for the centralized management, leading, or coordinating node, and when you discuss the relationship of that node with other nodes that interact with it. See manager node in the Splexicon.

Don't use. Use "main branch" instead.

Use only to mean permission. Use "might" for possibility or "can" for ability.

Use as a singular mass noun. Write "metadata is" rather than "metadata are".

Use to mean possibility.

Don't use. Use "dialog box" instead.

Use when referring to an icon with 3 horizontal dots (  ) or 3 vertical dots (  ) in a Splunk GUI. Don't capitalize. Include an inline image of the icon when possible.

Don't use. Use "hover over" instead.

Don't include a hyphen in words that begin with the prefix "multi".

Use instead of "multivalued field". See multivalue field in the Splexicon.

Don't use. Use "multivalue field" instead.

Write in lowercase letters. Use only in tables or lists to refer to a value that is not applicable or not available. Spell out instead of abbreviating when used in paragraph text.

Don't use. Use "hard-to-find" instead.

Use to refer to parts of documentation or page elements that immediately follow a user's current location in a topic, such as "in the next section".

If appropriate, you can also use "following" and "later".

Don't include a hyphen.

Use instead of "abnormal".

Don't use in text. Consider whether using a note admonition is more effective.

Use instead of "at present".

Write in lowercase letters to refer to an empty value, the null Search Processing Language (SPL) command, or when null appears in SPL search results.

Don't use. Use "on-premises" instead.

Include a hyphen and treat "premises" as plural. Use instead of "on premise", "on-premise", "on prem", or "on-prem".

Use when you mean 1 time and no more. Don't use to mean "after" or "when".

Place immediately before or after the word or phrase it modifies.

Use instead of "takes you to" or "launch".

Don't use. Use "default" or "prepackaged" instead.

Don't use. Use "update".

Use instead of "path name" or "pathname".

Don't use. Use "path" instead.

Use a numeral followed by the percent sign ( % ) to specify an exact percentage. Don't use the word "percent".

Use instead of "slave".

Use as a noun when not specifying an exact quantity.

Don't use in the context of searches or other commands. Use "run" instead.

If there are multiple ways a user can interact with a touch-based interface, use an input-agnostic term such as "zoom out" instead of "pinch".

If you must specify the user's gesture in order to perform an action on a mobile device, you can use "pinch".

Use instead of "dummy data".

Don't use.

Use "plug in" as a verb. Use "plugin" as a noun or adjective. Don't use "plug-in".

Don't use. Use "plug in" instead for a verb, or use "plugin" for a noun or adjective.

Write with capital letters and without periods. Use to mean between noon and 11:59 in the evening when writing the time of day.

Don't use. Use "hover over" instead.

Don't use. Use "dialog box" instead.

Don't use. Use "configured" instead.

Don't use. Use the name of the app instead or describe the apps in another way.

Don't use. Use the name of the app instead or describe the apps in another way.

Use instead of "out-of-the-box".

Don't use. Use "select" for the action of keying in characters on a keyboard or activating a button.

Use to refer to parts of documentation or page elements that immediately precede a user's current location, such as "in the previous section". If appropriate, you can also use "earlier".

Don't use. Use "enter" instead.

Don't use. Use "delete", "clear", or "remove" instead.

Use when referring to a SQL command or a database. To refer to a Splunk search, use "search" instead of "query".

Don't use.

Use to refer to the UI element. Don't use "radio" as a noun when referring to a radio button.

Include a hyphen. Use as an adjective.

Use the forward slash instead of a hyphen when you write about read, write, and delete permissions.

Use "real time" when used as a noun. Use "real-time" when used as an adjective.

Don't use. Use "real time" instead.

Don't use.

Use "reboot" only when it's part of a command. In most cases, use "restart" instead.

Don't use. Rewrite to state what the customer must do.

Use instead of "re-enable". Alternatively, use "enable again".

Don't use. Use "reenable" or "enable again" instead.

Use instead of "re-enter". Alternatively, rewrite as "enter again".

Don't use. Use "reenter" or "enter again" instead.

Don't use. Use "regular expression" instead.

Use instead of "regex".

Use instead of "purge". Alternatively, use "clear" or "delete".

Use instead of "re-run". Alternatively, use "run again".

Don't use. Use "rerun" or "run again" instead.

Use instead of "reboot".

Use instead of "fetch".

Use instead of "sanity check".

Don't use to refer to a location in a document. Use temporal language, such as "earlier", "previous", "following", "next", or "later".

Directional or visual instructions are unhelpful to visually impaired users, and locations of elements can change depending on the device being used to read the content.

Use in the context of searches or other commands. Don't use "execute" or "perform".

Use as an alternative option to "rerun". Use "again" only if it is necessary for clarity.

Use as a noun or adjective. Don't use "run time" or "run-time".

Don't write a lowercase "s" or "es" in parentheses after a noun to indicate both singular and plural.

Choose the best option for your sentence. In most cases, using the plural works best for understanding.

Don't use Supporting Add-on or the abbreviation "SA" when you write about the product. Use "add-on" instead.

It's okay to use "SA" in a file or path.

Use instead of "bulletproof". Alternatively, use "secure".

Don't use. Use "review" or "verification" instead.

Don't use. Use "read" or another device-agnostic verb that describes the intended action.

Use instead of "query" to refer to a Splunk search. See search in the Splexicon.

Use instead of "bulletproof". Alternatively, use "safe".

Use instead of "check out" for references and cross-references. To describe the UI, use "view" instead.

Use to highlight text, choose menu items, go to a link, push a button, open a tab, check a check box, or interact with a keyboard. Don't use "specify", "click", or "press".

Use this term to cover the multiple ways a user can interact with a touch-based interface.

If you must specify the user's gesture in order to perform an action on a mobile device, you can use "long press".

Because the term "server" is used in the IT industry to refer both to a type of software and the machine that the software runs on, avoid this term. Be clear when you refer to the Splunk platform.

Use "instance" in the Splunk platform context and "machine" for the virtual or physical machine the instance runs on.

Don't use in documentation. Use "they", "them", their", "a user", "the users", or another inclusive term.

Don't use. Avoid the subjunctive mood, and use imperative or indicative mood instead.

Use instead of "demonstrate" to mean illustrating or explaining with examples.

Don't use. Use "appears" instead.

Don't use. Use "log in" instead.

Don't use.

Don't use. Use "peer" for nodes that interact with the centralized management, leading, or coordinating node.

Use "sourcetype" when referring to the field name. Use "source type" in all other instances. See source type in the Splexicon.

Include a hyphen when used as an adjective.

Use "sparkle icon" or "AI sparkle icon" to refer to the icon for an AI assistant in a Splunk GUI (  ). Don't use "starburst icon", and don't capitalize. Include an inline image of the icon when possible.

Don't use in task steps. Use "select" or "enter" instead.

Don't use.

Don't use. Use "stop" and "start", or use the most descriptive action for the virtual machine.

When used alone, use "Splunk" to refer only to the company, not to any product. Don't use in the possessive form.

Use as a proper noun to refer to the software, spelled with initial capital letters. Don't include a definite article, use as a possessive, or shorten the name using an acronym or abbreviation.

Use as a proper noun to refer to https://dev.splunk.com, spelled with initial capital letters and using a definite article. Don't use abbreviations or acronyms in place of this term. Don't confuse this term with the Splunk Developer Program.

Don't use in documentation. This term refers to the program containing developer offerings like services, tooling, and the Splunk Developer Portal.

Don't confuse this term with the Splunk Developer Portal itself, which refers to https://dev.splunk.com.

Use as a proper noun to refer to the software, spelled with initial capital letters. Don't include a definite article or use as a possessive.

Use to refer to the product suite. Don't omit "Splunk" or use an acronym to shorten the name. Don't include a definite article or use as a possessive. Don't refer to the suite as a platform.

Use to refer to both Splunk Cloud Platform and Splunk Enterprise. Don't capitalize "platform" or use as a possessive. Include a definite article in most cases. Use as a modifier when writing about an instance, a deployment, or an environment when you're describing multiple platform products.

Don't use to refer to the icon for an AI assistant in a Splunk GUI (  ). Use "sparkle icon" or "AI sparkle icon" instead.

Use to refer to any combination of Splunk Enterprise, Splunk Cloud Platform, any Splunk-supported apps and add-ons, and any other software produced by Splunk. Don't capitalize "software" or use it as a possessive.

Use to refer to the portal where customers with a support contract can get assistance from Splunk Customer Support.

Capitalize the initial letters.

Use only in reference to the product called Splunk UI. For all other cases, use "Splunk Web".

Use to refer to the graphical user interface for the Splunk platform. See Splunk Web in the Splexicon.

Use when referring specifically to the Splunk Enterprise process, the service that is installed with Splunk Enterprise on Windows machines, or a service used to manage the splunkd process on Linux machines. Don't use in place of Splunk Enterprise or the Splunk platform. See splunkd in the Splexicon.

If there are multiple ways a user can interact with a touch-based interface, use an input-agnostic term such as "zoom in" instead of "spread".

If you must specify the user's gesture in order to perform an action on a mobile device, you can use "spread".

Use as a noun. Don't use as a verb.

Use only in specific cases where the word "stack" is used, like in the name of a CLI command or an API. Don't use to refer to a Splunk Cloud Platform deployment.

Write as 1 word with no hyphen. Use this term only as an adjective. Don't use "stand alone" or "stand-alone".

Use instead of "spin up".

Use instead of "spin down".

Use instead of "hangs".

Don't use. Use "time until restart" or choose another unambiguous term.

Use as a noun to describe the moveable slider bar in the UI that switches between on and off states.

It's okay to say "switch", "switch component", "toggle", or "toggle switch".

Use instead of "synch".

Don't use. Use "sync" or "synchronize" instead.

Don't use Technology Add-on or the abbreviation "TA" when you write about the product. Use "add-on" instead.

It's okay to use "TA" in a file or path.

Don't use. Use "open" instead.

If there are multiple ways a user can interact with a touch-based interface, use an input-agnostic term such as "select" instead of "tap".

If you must specify the user's gesture in order to perform an action on a mobile device, you can use "tap".

Don't use. Use "TAR file" instead.

Use instead of "tarball".

Don't use. Rewrite to be user-focused.

Use instead of "via".

Don't use.

Don't use. Use "time series" as a noun or "time-series" as an adjective.

Use "time series" when using as a noun. Use "time-series" when using as an adjective. See time series

in the Splexicon.

Use instead of "suicide mode".

Use as a verb to describe moving a switch component between on and off states. Use as a noun to describe the moveable slider bar in the UI that switches between on and off states.

It's okay to also call it a "switch", "switch component", or "toggle switch".

Use instead of "first-class entity".

Don't use to describe user input. Avoid terms that are specific to certain devices and input methods. Use "enter" instead.

Use "UNIX" if only UNIX is supported. Write "*nix" when referring to both UNIX and Linux.

Use instead of "epoch time".

Use instead of "fatal".

Use instead of "patch".

Don't use. Instead, clarify the action.

Use "URI" or "URL" instead of "URN" when referring to the respective string type. Choose the most specific initialism for your scenario.

Don't use. Use "URI" instead.

Use instead of "leverage" or "utilize".

Use as 2 words instead of "userbase".

Don't use. Use "user base" instead.

Use "username" in written text.

If "user name" appears as 2 words in the UI, write "user name" as 2 words in the documentation to match.

Don't use. Use "use" instead.

Don't use. Spell out "version" instead of abbreviating with a "v".

Use instead of "sanity check".

Use instead of "v" to indicate the software version.

Use instead of "vs.".

Alternatively, use "or", "as opposed to", or another appropriate term.

Don't use.

Don't use. Use "approved" instead.

Don't use Latin abbreviations or terms. Use "by using" or "through" instead.

Don't use Latin abbreviations or terms. Use "and the reverse" instead.

Use to refer to the validated architecture of Splunk Cloud Platform. Always capitalize. Don't include the definite article and don't use "Victoria" on its own.

Use with the preposition "on" when describing how to use an Experience or its components. Always refer to "Experience" in the same sentence when describing the designation.

Use instead of "see" to describe the UI.

Don't use in the context of websites. Use "go to", "navigate to", or another phrase.

Don't use. Use "versus" or another phrase instead.

Use instead of "desire" or "wish" to show hope for or to express a need.

Lowercase unless it is part of a proper name, like Splunk Web or World Wide Web.

Use to indicate an action, behavior, or event that is expected or certain to occur. This term implies a cause-and-effect relationship.

Use instead of "whether or not".

Don't use. Use "whether" instead.

Don't use. Use "allow list" as a noun and "allow" or "include" as a verb. For a single item, use "allow rule" or "allow entry".

There are additional synonyms you can use in specific situations. "Allow" refers to access, "accept" refers to validity, and "include" refers to inclusion. For IP traffic, for example, "allow" is suitable. For files or rules, "include" might be more specific.

Don't use. Use "wildcard" with an asterisk in parentheses after the term to denote the search action of matching characters in string values.

Don't use. Use "want" instead.

Avoid using this term. Use only if you need to refer to the UI component and the label contains the word "wizard". If you must refer to the general component, use "guided setup" sparingly. Always aim to describe the user's actions and goals instead of the components and features of the product.

Don't use. Avoid subjunctive mood. Write in the indicative or imperative mood instead.

Use a lowercase "x" to represent a range of HTTP status codes.

Use a lowercase "x" at the relevant place in the version number when referring to maintenance builds, minor versions, or releases for a product. Don't include a "v" before the number.