Index: docs/P2-RelationalDesign/RelationalDesign.md
===================================================================
--- docs/P2-RelationalDesign/RelationalDesign.md	(revision b715712c7d5d3ee27c932a8a9d8e0a2bc6e85127)
+++ docs/P2-RelationalDesign/RelationalDesign.md	(revision df058387ebe7d07864d874fd1376f15512418581)
@@ -96,5 +96,5 @@
 ![relational_schema](relational_schema.jpg)
 
-Generated in **DBeaver** from the **live** `project` schema, in crow's-foot
+Generated in **Pgadmin** from the **live** `project` schema, in crow's-foot
 notation — not drawn by hand, so it is evidence that the deployed database
 actually matches the design described above. Each box is a table with its
@@ -103,21 +103,4 @@
 
 ### How to regenerate it
-
-**With DBeaver** (the tool the course recommends):
-
-1. Connect to the assigned FINKI PostgreSQL project database.
-2. Double-click the `project` schema → **ER Diagram** tab.
-3. Right-click in the diagram → **Notation** → **Crow's foot**.
-4. Arrange the tables to mirror the layout of
-   [`ERModel_v01.png`](../P1-ConceptualModel/ERModel_v01.png).
-5. Right-click → **Export diagram** → save as `relational_schema.jpg`.
-
-On Linux, install it with:
-
-```sh
-flatpak remote-add --if-not-exists --user flathub https://dl.flathub.org/repo/flathub.flatpakrepo
-flatpak install --user flathub io.dbeaver.DBeaverCommunity
-# or:  sudo snap install dbeaver-ce
-```
 
 **With pgAdmin 4**, if DBeaver is unavailable — it reads the live schema the same
@@ -131,7 +114,2 @@
    `convert relational_schema.png relational_schema.jpg`
 
-Whichever tool is used, state it here so the choice is explicit rather than
-inferred. Do **not** substitute a tool that only reads the `.sql` file — such as
-dbdiagram.io — because the diagram would then show what the script says rather
-than what the deployed database contains, which is the thing this artefact is
-meant to demonstrate.