Skip to content

Commit 63dfbf5

Browse files
v-makoudzivkan
authored andcommitted
C55619: Moving space after asterisk in "*any *" as "*any* " (NuGet#1225)
Hello @karann-msft, Translator has reported possible source content issue. Please review and merge the suggested proposed file change to avoid this error. If you make related fix in another PR, then share your PR number, so we can confirm and close this PR. Many thanks in advance.
1 parent a1e642c commit 63dfbf5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/create-packages/Prerelease-Packages.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ In this convention, each version has three parts, `Major.Minor.Patch`, with the
5959
- `Minor`: New features, but backwards compatible
6060
- `Patch`: Backwards compatible bug fixes only
6161

62-
Pre-release versions are then denoted by appending a hyphen and a string after the patch number. Technically speaking, you can use *any *string after the hyphen and NuGet will treat the package as pre-release. NuGet then displays the full version number in the applicable UI, leaving consumers to interpret the meaning for themselves.
62+
Pre-release versions are then denoted by appending a hyphen and a string after the patch number. Technically speaking, you can use *any* string after the hyphen and NuGet will treat the package as pre-release. NuGet then displays the full version number in the applicable UI, leaving consumers to interpret the meaning for themselves.
6363

6464
With this in mind, it's generally good to follow recognized naming conventions such as the following:
6565

0 commit comments

Comments
 (0)