more formatting

forester123 · Jun 1, 2017 · aa5188b · aa5188b
1 parent 051c979
commit aa5188b
Showing 1 changed file with 5 additions and 1 deletion.
diff --git a/articles/azure-resource-manager/resource-manager-template-child-resource.md b/articles/azure-resource-manager/resource-manager-template-child-resource.md
@@ -27,9 +27,13 @@ The format of the child resource name is: `{parent-resource-name}/{child-resourc
 However, you specify the type and name in a template differently based on whether it is nested within the parent resource, or on its own at the top level. This topic shows how to handle both approaches.
 
 When constructing a fully qualified reference to a resource, the order to combine segments from the type and name  is not simply a concatenation of the two.  Instead, after the namespace, use a sequence of *type/name* pairs from least specific to most specific:
-`{resource-provider-namespace}/{parent-resource-type}/{parent-resource-name}[/{child-resource-type}/{child-resource-name}]*`
+
+```json
+{resource-provider-namespace}/{parent-resource-type}/{parent-resource-name}[/{child-resource-type}/{child-resource-name}]*
+```
 
 For example:
+
 `Microsoft.Compute/virtualMachines/myVM/extensions/myExt` is correct
 `Microsoft.Compute/virtualMachines/extensions/myVM/myExt` is not correct