---
title: p.step.informal.command
description: "## Syntax **p.step.informal.command(**level**)** level is the nesting depth of the step. Migrate allows for steps to be nested at depths of 1 or 2. ** ** ## Purpose The p.step.informal.command annotation is used to tag an element as being a step…"
url: "https://www.stilo.com/docs/migrate/migrate-and-dita/p-step-informal-command/"
updated: "2023-12-05"
category: Annotations / Migrate and DITA
tags:
  - Annotations
---

# p.step.informal.command

## Syntax

**p.step.informal.command(**level**)**

level is the nesting depth of the step. Migrate allows for steps to be nested at depths of 1 or 2.

** **

## Purpose

The p.step.informal.command annotation is used to tag an element as being a step containing contextual or other descriptive information. This element can contain multiple steps, a combination of steps and non-procedural information, or both. This is a very casual method of presenting procedural information.

## Examples

The following is an example of a time when you might want to use the p.step.informal.command annotation:

![](https://www.stilo.com/wp-content/uploads/2023/11/stilo-dita-xml-annotation-p.step_.informal.command0.png)

The following is an example of a rule that will apply p.step.informal.command:

![](https://www.stilo.com/wp-content/uploads/2023/11/stilo-dita-xml-annotation-p.step_.informal.command1.png)

 

The following is an example of the DITA output you would get from this annotation.

 

<steps-informal><p id="ID-00000022">When you declare a variable with let or var, follow the same syntax as above. Using let allows you to reassign the variable at a later point in the code. Only use var when you need to support old browsers.</p></steps-informal>

````