From 669acf07257203aca5645eeea6f31aa704d28a11 Mon Sep 17 00:00:00 2001
From: MaximFworks <137869596+MaximFworks@users.noreply.github.com>
Date: Tue, 18 Mar 2025 11:07:54 +0200
Subject: [PATCH] Update Language-Interop-and-.NET.md

This is more accurate and informative.
---
 Best-Practices/Language-Interop-and-.NET.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Best-Practices/Language-Interop-and-.NET.md b/Best-Practices/Language-Interop-and-.NET.md
index f0d697b..cd0a29f 100644
--- a/Best-Practices/Language-Interop-and-.NET.md
+++ b/Best-Practices/Language-Interop-and-.NET.md
@@ -26,7 +26,7 @@ All that said, make sure you specify the version of PowerShell you wrote for by
 #requires -version 3.0
 ```
 
-The `#requires` statement will prevent the script from running on the wrong version of PowerShell.
+The `#requires` statement will make sure, that version of PowerShell is at least 3.0, or the script will exit with the error "ScriptRequiresUnmatchedPSVersion". You may still encounter problems if you run PowerShell 5.1 (.NET Framework) scripts on PowerShell 7+ (.NET Core).
 
 ### PowerShell Supported Version