diff --git a/docs/how-to-guides/effective-gno.md b/docs/concepts/effective-gno.md
similarity index 99%
rename from docs/how-to-guides/effective-gno.md
rename to docs/concepts/effective-gno.md
index fd7929e2289..ca593edf212 100644
--- a/docs/how-to-guides/effective-gno.md
+++ b/docs/concepts/effective-gno.md
@@ -1,5 +1,5 @@
 ---
-id: 'effective-gno'
+id: effective-gno
 ---
 
 # Effective Gno
@@ -82,7 +82,7 @@ Go developers "Don't panic.", in Gno, we actually embrace `panic`.
 
 Panic in Gno is not just for critical errors or programming mistakes as it is in
 Go. Instead, it's used as a control flow mechanism to stop the execution of a
-[realm](../concepts/realms.md) when something goes wrong. This could be due to an invalid input, a
+[realm](realms.md) when something goes wrong. This could be due to an invalid input, a
 failed precondition, or any other situation where it's not possible or desirable
 to continue executing the contract.
 
diff --git a/misc/docusaurus/sidebars.js b/misc/docusaurus/sidebars.js
index 36f53aeca0a..b6317cbbae0 100644
--- a/misc/docusaurus/sidebars.js
+++ b/misc/docusaurus/sidebars.js
@@ -34,7 +34,6 @@ const sidebars = {
                 'how-to-guides/creating-grc20',
                 'how-to-guides/creating-grc721',
                 'how-to-guides/connect-wallet-dapp',
-                'how-to-guides/effective-gno',
             ],
         },
         {
@@ -53,10 +52,11 @@ const sidebars = {
                         'concepts/standard-library/gnopher-hole-stdlib',
                     ]
                 },
-                'concepts/tendermint2',
                 'concepts/gnovm',
-                'concepts/proof-of-contribution',
                 'concepts/gno-language',
+                'concepts/effective-gno',
+                'concepts/proof-of-contribution',
+                'concepts/tendermint2',
                 'concepts/gno-modules',
                 'concepts/gno-test',
                 'concepts/from-go-to-gno',