From 46a28a2ada4c16f109205372f268df35fc41fade Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=D0=90=D0=BB=D0=B5=D0=BA=D1=81=D0=B0=D0=BD=D0=B4=D1=8A?=
 =?UTF-8?q?=D1=80=20=D0=9A=D1=83=D1=80=D1=82=D0=B0=D0=BA=D0=BE=D0=B2?=
 <akurtakov@gmail.com>
Date: Thu, 2 Oct 2025 12:12:29 +0300
Subject: [PATCH] Update Eclipse4_RCP_Contexts.md

---
 docs/Eclipse4_RCP_Contexts.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/Eclipse4_RCP_Contexts.md b/docs/Eclipse4_RCP_Contexts.md
index 1ce77da041b..1cd78594068 100644
--- a/docs/Eclipse4_RCP_Contexts.md
+++ b/docs/Eclipse4_RCP_Contexts.md
@@ -77,11 +77,13 @@ There are many active branches in a context tree, but there is only ever a singl
 A node can be made active in two ways. 
 Calling _#activate()_ makes the receiver the active child of its parent node, but does not otherwise disturb the rest of the tree. 
 Calling _#activateBranch()_ on the other hand effectively the same as:
+```java
 
        void activateBranch() {
           activate();
           if(getParent() != null) getParent().activateBranch(); 
        }
+```
 
 It makes the receiver the active child of its parent, and then recursively calls _#activateBranch()_ on its parent.