XS✔ ◾ Fix broken build - archived reason includes colon “:” (#8113)

* Fix broken build - archived reason includes colon “:”

* Update rule.md

rules/avoid-using-non-strongly-typed-connection-strings/rule.md

@@ -6,7 +6,7 @@ authors:
   - title: Igor Goldobin
     url: https://ssw.com.au/people/alumni/igor-goldobin/
 created: 2024-03-09T06:15:30.110Z
-archivedreason: Update connection string management: favor IOptions pattern over Visual Studio's Application Settings. Offers robust, flexible config in .NET Core, aligning with modern development practices. Refer to Microsoft's IOptions pattern in .NET documentation for implementation guidance.
+archivedreason: Update connection string management - favor IOptions pattern over Visual Studio's Application Settings. Offers robust, flexible config in .NET Core, aligning with modern development practices. Refer to Microsoft's IOptions pattern in .NET documentation for implementation guidance.
 guid: 27abe1ac-b34a-4ea7-94e5-a3cd5ba5e10b
 ---
 Using non strongly typed connection strings means that you have to hard code at some point in your code. Once you change the name of your connection strings, you have to change the code that references them too.