diff --git a/10 Notes/High-Level Solution Proposal.md b/10 Notes/High-Level Solution Proposal.md
index 850f92b..bc5aed6 100644
--- a/10 Notes/High-Level Solution Proposal.md	
+++ b/10 Notes/High-Level Solution Proposal.md	
@@ -130,11 +130,11 @@ Finally, the corresponding torrent file is (re)created, the `HistoryArchivesCrea
 
 The diagram below shows the relationships between the datatypes described above:
 
-![[team-nl-br-design-1.svg]]
+![[codex-status-go-design-1.svg]]
 
 And then in the following diagram we show how the `index` and `data` files are populated, the corresponding torrent file and the magnet link:
 
-![[team-nl-br-design-2.svg]]
+![[codex-status-go-design-2.svg]]
 
 ## Archive Distribution and Download
 
@@ -172,7 +172,7 @@ In order to receive the historical messages for the given period (given by `from
 
 The diagram below shows the relationship between the new `index` identified by a Codex CID that uses individual CIDs to refer to each individual archive:
 
-![[team-nl-br-design-3.svg]]
+![[codex-status-go-design-3.svg]]
 
 ### Advantages
 
@@ -191,7 +191,7 @@ In the first prototype, we suggest to use Codex API in order to validate the ide
 
 Creating the Codex library was not only long requested by IFT, but it also bring opportunity to rethink the system interfaces and work towards more modular, "plugable" design. In its first instance Codex library could be made of just the block-exchange protocol, discovery module (DHT), and *RepoStore* (block storage) - each of those could potentially be also separated into separate sub-libraries. By providing bindings for various programming languages, we can better stimulate community clients, our original Codex client being one of them. The illustration below shows a high-level overview of the composition and use of the Codex library.
 
-![[team-nl-br-design-4.svg]]
+![[codex-status-go-design-4.svg]]
 
 ## Changes required in the status-go client
 
diff --git a/10 Notes/status-go-codex integration - design notes.md b/10 Notes/status-go-codex integration - design notes.md
index bed2500..f6169ec 100644
--- a/10 Notes/status-go-codex integration - design notes.md	
+++ b/10 Notes/status-go-codex integration - design notes.md	
@@ -203,7 +203,7 @@ This data file is temporary and will be overwritten for each new archive created
 
 Now, just for convenience, let's recall the original data structures involved:
 
-![[team-nl-br-design-1.svg]]
+![[codex-status-go-design-1.svg]]
 
 The data structures using with BitTorrent are:
 
diff --git a/90 Extras/92 Assets/team-nl-br-design-1.svg b/90 Extras/92 Assets/codex-status-go-design-1.svg
similarity index 100%
rename from 90 Extras/92 Assets/team-nl-br-design-1.svg
rename to 90 Extras/92 Assets/codex-status-go-design-1.svg
diff --git a/90 Extras/92 Assets/team-nl-br-design-2.svg b/90 Extras/92 Assets/codex-status-go-design-2.svg
similarity index 100%
rename from 90 Extras/92 Assets/team-nl-br-design-2.svg
rename to 90 Extras/92 Assets/codex-status-go-design-2.svg
diff --git a/90 Extras/92 Assets/team-nl-br-design-3.svg b/90 Extras/92 Assets/codex-status-go-design-3.svg
similarity index 100%
rename from 90 Extras/92 Assets/team-nl-br-design-3.svg
rename to 90 Extras/92 Assets/codex-status-go-design-3.svg
diff --git a/90 Extras/92 Assets/team-nl-br-design-4.svg b/90 Extras/92 Assets/codex-status-go-design-4.svg
similarity index 100%
rename from 90 Extras/92 Assets/team-nl-br-design-4.svg
rename to 90 Extras/92 Assets/codex-status-go-design-4.svg