diff --git a/public/roadmap-content/postgresql-dba.json b/public/roadmap-content/postgresql-dba.json
index 4279d8fa1..3ca150d8d 100644
--- a/public/roadmap-content/postgresql-dba.json
+++ b/public/roadmap-content/postgresql-dba.json
@@ -1075,7 +1075,7 @@
     ]
   },
   "S20aJB-VuSpXYyd0-0S8c": {
-    "title": "Object Priviliges",
+    "title": "Object Privileges",
     "description": "Object privileges in PostgreSQL are the permissions given to different user roles to access or modify database objects like tables, views, sequences, and functions. Ensuring proper object privileges is crucial for maintaining a secure and well-functioning database.\n\nLearn more from the following resources:",
     "links": [
       {
@@ -1117,7 +1117,7 @@
     ]
   },
   "t18XjeHP4uRyERdqhHpl5": {
-    "title": "Default Priviliges",
+    "title": "Default Privileges",
     "description": "PostgreSQL allows you to define object privileges for various types of database objects. These privileges determine if a user can access and manipulate objects like tables, views, sequences, or functions. In this section, we will focus on understanding default privileges in PostgreSQL.\n\nLearn more from the following resources:",
     "links": [
       {
@@ -2900,4 +2900,4 @@
     "description": "If you are an experienced developer or willing to learn, you can contribute to PostgreSQL by writing patches. Patches are important to fix bugs, optimize performance, and implement new features. Here are some guidelines on how to write patches for PostgreSQL:\n\n### Step 1: Find an Issue or Feature\n\nBefore writing a patch, you should identify an issue in PostgreSQL that needs fixing or a feature that requires implementation. You can find existing issues or propose new ones in the [PostgreSQL Bug Tracker](https://www.postgresql.org/support/submitbug/) and [PostgreSQL mailing lists](https://www.postgresql.org/list/).\n\n### Step 2: Familiarize Yourself with the Codebase\n\nTo write a patch, you must have a good understanding of the PostgreSQL source code. The code is available on the [official website](https://www.postgresql.org/developer/sourcecode/) and is organized into different modules. Familiarize yourself with the coding conventions, coding style, and the appropriate module where your patch will be applied.\n\n### Step 3: Set up the Development Environment\n\nTo create a patch, you need a development environment with the required tools, such as Git, GCC, and Bison. Follow the instructions in the [PostgreSQL Developer Setup Guide](https://wiki.postgresql.org/wiki/Developer_Setup) to set up your environment.\n\n### Step 4: Write the Patch\n\nEnsure that your patch adheres to the [PostgreSQL Coding Conventions](https://www.postgresql.org/docs/current/source-format.html). This includes following proper indentation, formatting, and organizing your code. Write clear and concise comments to help others understand the purpose of your patch.\n\n### Step 5: Test the Patch\n\nBefore submitting your patch, thoroughly test it to ensure it works correctly and does not introduce new issues. Run the patch through the PostgreSQL regression test suite, as well as any additional tests specific to your patch.\n\n### Step 6: Create a Commit and Generate a Patch\n\nAfter completing your patch and testing it, create a Git commit with a clear and concise commit message. Use `git-format-patch` to generate a patch file that can be submitted to the PostgreSQL project.\n\n### Step 7: Submit the Patch\n\nOnce your patch is ready, submit it through the appropriate [PostgreSQL mailing list](https://www.postgresql.org/list/) for review. Be prepared to receive feedback, make revisions, and resubmit your patch if necessary. Remember, contributing to an open-source project like PostgreSQL is a collaborative process!\n\nBy following these steps, you will be well on your way to contributing to the PostgreSQL project by writing patches. Happy coding!",
     "links": []
   }
-}
\ No newline at end of file
+}
diff --git a/src/data/roadmaps/postgresql-dba/content/default-priviliges@t18XjeHP4uRyERdqhHpl5.md b/src/data/roadmaps/postgresql-dba/content/default-privileges@t18XjeHP4uRyERdqhHpl5.md
similarity index 100%
rename from src/data/roadmaps/postgresql-dba/content/default-priviliges@t18XjeHP4uRyERdqhHpl5.md
rename to src/data/roadmaps/postgresql-dba/content/default-privileges@t18XjeHP4uRyERdqhHpl5.md
diff --git a/src/data/roadmaps/postgresql-dba/content/object-priviliges@S20aJB-VuSpXYyd0-0S8c.md b/src/data/roadmaps/postgresql-dba/content/object-privileges@S20aJB-VuSpXYyd0-0S8c.md
similarity index 100%
rename from src/data/roadmaps/postgresql-dba/content/object-priviliges@S20aJB-VuSpXYyd0-0S8c.md
rename to src/data/roadmaps/postgresql-dba/content/object-privileges@S20aJB-VuSpXYyd0-0S8c.md
diff --git a/src/data/roadmaps/postgresql-dba/postgresql-dba.json b/src/data/roadmaps/postgresql-dba/postgresql-dba.json
index 8d80d4fae..86736f406 100644
--- a/src/data/roadmaps/postgresql-dba/postgresql-dba.json
+++ b/src/data/roadmaps/postgresql-dba/postgresql-dba.json
@@ -2765,7 +2765,7 @@
       },
       "selected": false,
       "data": {
-        "label": "Object Priviliges",
+        "label": "Object Privileges",
         "style": {
           "fontSize": 17,
           "justifyContent": "flex-start",
@@ -2830,7 +2830,7 @@
       },
       "selected": false,
       "data": {
-        "label": "Default Priviliges",
+        "label": "Default Privileges",
         "style": {
           "fontSize": 17,
           "justifyContent": "flex-start",
@@ -8128,4 +8128,4 @@
       "focusable": true
     }
   ]
-}
\ No newline at end of file
+}