update

aws/documentation/naming-tagging-standard/naming/secretsmanager.md

@@ -17,7 +17,7 @@ For deployment to all accounts, defined from the organziation management account
 core accounts.  These are approved for user by the cloud architect before implementation. They will be listed [here](#secrets--enterprise)
 as well as documented under [secrets](secrets/).
 
-Format: /enterprise/{category}/{purpose}/[{region}/]{item}
+Format: `/enterprise/{category}/{purpose}/[{region}/]{item}`
 
 * segments will be all in lowercase, consist of the set including letters, digits, and underscore (a-z, 0-9, _)  
 * {category}  
@@ -43,7 +43,7 @@ This is not intended to be usable across all accounts, only within the account w
 organziation (or other OUs) will not be enabled.  This _may_ be used to override an **Enterprise** secret (logic to be defined by the user, but
 somethign like "look for /local/X by name, if not found, use /enterprise/X").
 
-Format: /local/{category}/{purpose}/[{region}/]{item}
+Format: `/local/{category}/{purpose}/[{region}/]{item}`
 
 The same format rules apply as for `/enterprise` above.
 
@@ -52,7 +52,7 @@ The same format rules apply as for `/enterprise` above.
 This is how application areas will construct SecretsManager secret names.
 It uses components of the base label format, and includes the organization or program, project, and environment.
 
-Format: /app/{organization_program}/{project}/[{environment}/][{region}/]{item}
+Format: `/app/{organization_program}/{project}/[{environment}/][{region}/]{item}`
 
 The same format rules apply as for `/enterprise` above for the relevant field names.