Fixing formatting

v-dirichards · web-flow · commit a1b5778ec1c4 · 2025-04-01T15:32:12.000-05:00
diff --git a/docs/reporting-services/tools/server-properties-advanced-page-reporting-services.md b/docs/reporting-services/tools/server-properties-advanced-page-reporting-services.md
@@ -84,7 +84,7 @@ Sets header values for all URLs matching the specified regex pattern. Users can
 > Too many headers may impact performance.
 > 
 > The ```X-Frame-Options```default response header will block the ability to embed SSRS reports within an iframe html element. Removing this header from the ```<CustomHeaders />``` advanced server property will allow reports to be used within iframes.  
-> ** It is not recommended to make this change on any report servers that will be hosted on the public internet.
+> ** It is not recommended to make this change on any report servers that will be hosted on the public internet.**
 
 We recommend validating the configuration of your topology to ensure the set of headers is compatible with your deployment of Reporting Services. It's possible to choose settings that cause errors in browsers if the browsers don't also have the appropriate settings. For example, you shouldn't add an HSTS configuration if your server isn't configured for https. Incompatible headers might result in browser rendering errors.
 

Original file line number	Diff line number	Diff line change
`@@ -84,7 +84,7 @@ Sets header values for all URLs matching the specified regex pattern. Users can`
`84`	`84`	`> Too many headers may impact performance.`
`85`	`85`	`>`
`86`	`86`	> The ```X-Frame-Options```default response header will block the ability to embed SSRS reports within an iframe html element. Removing this header from the ```<CustomHeaders />``` advanced server property will allow reports to be used within iframes.
`87`		`-> ** It is not recommended to make this change on any report servers that will be hosted on the public internet.`
	`87`	`+> It is not recommended to make this change on any report servers that will be hosted on the public internet.`
`88`	`88`
`89`	`89`	`We recommend validating the configuration of your topology to ensure the set of headers is compatible with your deployment of Reporting Services. It's possible to choose settings that cause errors in browsers if the browsers don't also have the appropriate settings. For example, you shouldn't add an HSTS configuration if your server isn't configured for https. Incompatible headers might result in browser rendering errors.`
`90`	`90`