diff --git a/docs/development/RELEASE.md b/docs/development/RELEASE.md
index 01e24e345..6cca0625e 100644
--- a/docs/development/RELEASE.md
+++ b/docs/development/RELEASE.md
@@ -14,7 +14,7 @@ The automated process handles
 - Creating Git tag using the version number
 - Creating a commit bumping the version number up in `package.json`
 - Creating GitHub Release
-- Creating [VEDA configuration instance](https://github.com/nasa-impact/veda-config) preview using VEDA UI version (When the release is made from `main` branch)
+- Creating [Earth Data instance](https://github.com/nasa-impact/veda-config) preview using VEDA UI version (When the release is made from `main` branch)
 
 After the last step, we can manually test if the release did not introduce any unexpected regression through the Preview URL.
 
@@ -28,7 +28,7 @@ If you are a contributor, you can trigger a release action through the Actions t
 
 #### Instance Build
 
-Upon triggering, the GitHub Action builds the [Configuration (veda-config) instance](https://github.com/nasa-impact/veda-config) using the specified release. It will create a Pull Request, as shown below, on veda-config, building a preview using the released UI.
+Upon triggering, the GitHub Action builds the [Earth Data (veda-config) instance](https://github.com/nasa-impact/veda-config) using the specified release. It will create a Pull Request, as shown below, on veda-config, building a preview using the released UI.
 
 ![Screenshot of generated PR ](../media/preview-pr.png)