diff --git a/knowledge-base/add-license-key-openedge.md b/knowledge-base/add-license-key-openedge.md
index 7822f5ecb..ecc0c6bf2 100644
--- a/knowledge-base/add-license-key-openedge.md
+++ b/knowledge-base/add-license-key-openedge.md
@@ -20,7 +20,9 @@ I work in an OpenEdge environment and need to activate my Telerik UI for WinForm
 
 ## Solution
 
-The following tutorial will demonstrate how to set up your license key in the OpenEdge environment.
+In OpenEdge ABL applications, it is crucial to register the Telerik WinForms license key before any Telerik control, form, or component is initialized — especially if your application starts with a Telerik form. The following tutorial demonstrates how to set up your license key in the OpenEdge environment, either in a Form or in a procedure file.
+
+### Registering the License Key in the Form
 
 1. Go to the [Setting Up Your Telerik UI for WinForms License Key](https://docs.telerik.com/devtools/winforms/licensing/license-key#downloading-the-license-key) and follow the first two sections of the article.
 	1. Downloading the License Key
@@ -28,7 +30,7 @@ The following tutorial will demonstrate how to set up your license key in the Op
 	
 1. Go to the [License Keys page](https://www.telerik.com/account/your-licenses/license-keys) in your Telerik account.
 
-1. On the Telerik UI for WinForms row, click the **View key** link in the **SCRIPT KEY** column. Copy only the string in the first Telerik.Licensing.EvidenceAttribute("key"). 
+1. On the Telerik UI for WinForms row, click the **View key** link in the **SCRIPT KEY** column. __Copy ONLY the key string in the first Telerik.Licensing.EvidenceAttribute("key").__ 
 
 	![copy-license-key](images/add-license-key-openedge.png)
 
@@ -37,7 +39,6 @@ The following tutorial will demonstrate how to set up your license key in the Op
 ````ABL
 
 CONSTRUCTOR PUBLIC Form1 (  ):        
-	// ActivePerpetual script key	
 	Telerik.Licensing.TelerikLicensing:Register("Your License Key").
 	
 	InitializeComponent().
@@ -57,6 +58,14 @@ END CONSTRUCTOR.
 
 >Do not publish the script license key snippet in publicly accessible repositories. This is your personal license key.
 
+### Registering the License Key in a Procedure File
+
+Unlike standard .NET applications, OpenEdge GUI applications always start from a procedure file (.p), not a class (.cls). This means there is always a non-GUI entry point where initialization code can safely run before any UI is loaded. 
+
+If registering the key inside a Form does not work — for example, when the first screen is a Telerik form — you should register the key earlier in your application's startup sequence. 
+
+For more advanced scenarios, including customizing the startup of your project, refer to the [Progress Developer Studio for OpenEdge Online Help](https://docs.progress.com/bundle/openedge-developer-studio-help/page/Customize-project-startup.html).
+
 
 ## See Also
 
diff --git a/knowledge-base/images/add-license-key-openedge.png b/knowledge-base/images/add-license-key-openedge.png
index 54cb5d5a8..0815f3c1a 100644
Binary files a/knowledge-base/images/add-license-key-openedge.png and b/knowledge-base/images/add-license-key-openedge.png differ