Fixed typo error in NumberFormatInfo.NegativeSign Property example

[prasadtelkikar]

Summary

In the example, an instance of CultureInfo is defined with the variable name ci. While converting a number into a string, culture variable is used instead of the variable name ci.

This PR contains, use of ci variable. This will resolve compile-time error.

Fixes #7552 Typo error in NumberFormatInfo.NegativeSign Property example

[dnfadmin]

All CLA requirements met.

[ghost]

Tagging subscribers to this area: @tarekgh, @safern
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Summary

In the example, an instance of CultureInfo is defined with the variable name ci. While converting a number into a string, culture variable is used instead of the variable name ci.

This PR contains, use of ci variable. This will resolve compile-time error.

Fixes #7552 Typo error in NumberFormatInfo.NegativeSign Property example

Author:	prasadtelkikar
Assignees:	-
Labels:	area-System.Globalization
Milestone:	-

[gewarren]

Thank you @prasadtelkikar. Could you add a .csproj and .vbproj file to the corresponding folders too? For .csproj, it's as simple as this: https://github.com/dotnet/dotnet-api-docs/blob/main/samples/snippets/csharp/api/system.io/path/combine/misc.csproj. That way the sample code can be compiled during PR checks.

[prasadtelkikar]

Hi @tarekgh ,

I raised PR against issue #7553, Kindly review it and let me know if there is anything I missed.
This is my First PR to dotnet-api-docs repository.

Happy coding.... 😇

Thanks,
Prasad

[opbld30]

Docs Build status updates of commit 478450f:

✅ Validation status: passed

File	Status	Preview URL	Details
samples/snippets/csharp/VS_Snippets_CLR_System/system.globalization.numberformatinfo.negativesign/cs/negativesign1.cs	✅Succeeded	View
samples/snippets/visualbasic/VS_Snippets_CLR_System/system.globalization.numberformatinfo.negativesign/vb/negativesign1.vb	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[tarekgh]

LGTM. Thanks @prasadtelkikar for fixing that.