Skip to content

Commit 577a0c4

Browse files
authored
Correct fenced-in code blocks (#700)
A couple of the code blocks have improper termination of their fenced-off markdown. Clean up those code blocks so they are rendered properly.
1 parent 61da103 commit 577a0c4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -187,8 +187,8 @@ You can suppress warnings for a specific file by adding `SuppressTSqlWarnings` f
187187
</Content>
188188
</ItemGroup>
189189
</Project>
190+
```
190191

191-
```bash
192192
> Note: Warnings suppressed at the project level are always applied to every file in the project, regardless of what is configured at the file level.
193193
194194
## Pre- and post deployment scripts
@@ -324,8 +324,8 @@ You can also use SQLCMD variables to set references, similar to the behavior of
324324
</SqlCmdVariable>
325325
</ItemGroup>
326326
</Project>
327+
```
327328

328-
```bash
329329
In this scenario you can access the objects defined by `MyDatabasePackage` by using the `[$(SomeOtherServer)].[$(SomeOtherDatabase)].[<schema>].[<object>]` syntax.
330330
Also you can combine `ServerSqlCmdVariable` with `DatabaseVariableLiteralValue` and use `[$(SomeOtherServer)].[SomeOtherDatabase].[<schema>].[<object>]` syntax.
331331

0 commit comments

Comments
 (0)