From 3a0cf06279020746a71aac94ca9b23401afd1da8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Zolt=C3=A1n=20Leh=C3=B3czky?= <zoltan.lehoczky@lombiq.com>
Date: Sat, 11 Jan 2025 02:39:15 +0100
Subject: [PATCH] Spelling

---
 .../IndirectPackageReference/IndirectPackageReference.csproj    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/TestSolutions/Lombiq.Analyzers.PackageReference/IndirectPackageReference/IndirectPackageReference.csproj b/TestSolutions/Lombiq.Analyzers.PackageReference/IndirectPackageReference/IndirectPackageReference.csproj
index 1150abe..49e720b 100644
--- a/TestSolutions/Lombiq.Analyzers.PackageReference/IndirectPackageReference/IndirectPackageReference.csproj
+++ b/TestSolutions/Lombiq.Analyzers.PackageReference/IndirectPackageReference/IndirectPackageReference.csproj
@@ -5,7 +5,7 @@
   </PropertyGroup>
 
   <!-- This project demonstrates that the package reference doesn't transfer the analyzer effect to its dependents. If
-       you set ImportPackageAgain to "true" and run static code analysis on this soltuion you will get twice as many
+       you set ImportPackageAgain to "true" and run static code analysis on this solution you will get twice as many
        warnings. This is the desired behavior, shows that the analyzers only activate when they are explicitly imported.
   -->