diff --git a/docs/our_work/ds251_RAG.md b/docs/our_work/ds251_RAG.md
index e2233c75..307470bd 100644
--- a/docs/our_work/ds251_RAG.md
+++ b/docs/our_work/ds251_RAG.md
@@ -2,33 +2,10 @@
 title: 'Retrieval Augmented Generation'
 summary: 'Investigating Advanced RAG, collaborating with efforts to evaluate LLM outputs.'
 origin: ''
-tags: ['nlp','llm','genai']
+tags: ['NLP','LLM','GENAI']
 ---
-[comment]: <> When making your tags, it might be handy to see a list of the tags that have already been defined. Run `python utils/list-tags.py` from the terminal to print the existing tags (assuming you are in the root directory - update the path if not). You can also run it from VS Code by opening the file and clicking the "Run" button in the top right (but you'll need to have the Python extension installed to do it this way).
 
-[comment]: <> The metadata block above is used to make the title, the tags, and the first block of "quote text" just beneath the title
+## PLACEHOLDER PAGE - CONTENT COMING SOON!
 
-[comment]: <> Make a nice visual abstract for your project, or show some key result, which makes the impact of your work clear - imagine your audience is an educated observer from the health system
-[![Alt text for the image](../images/<add your age to the image folder and put the file name here>)](<add a relevant URL if you have one - people like to click images!>)
-
-[comment]: <> Add some description about your project - keep it punchy, focussing on the benefits, anything new, and only the most important parts of the methods, particularly anything which might interest people.
-
-People often have this problem - we used data science to make the solution. We worked with patient groups / clinicians /  senior decision makers to come up with a solution which use AI, etc., we were able to automate this task.
-
-## Results
-
-[comment]: <> Add some description of the key results - again keep them punchy, and in real units that people can understand if possible. This is where we get across the impact. It might be that the image describes this, in which case reference that.
-by automating the problem area described above, we were able to save £xxx / so many hours of doctor / patient / staff time. The diagram above shows how impactful this was.
-
-Output|Link
-
-[comment]: <> below you can put any relevant links through to outputs, and published code, published papers, live tools, websites, blog articles, anything which is relevant to the project.
----|---
-Open Source Code & Documentation|[Github](#add URL)
-Case Study|
-Technical report|[e.g. biorxiv.org]()
-Algorithmic Impact Assessment|e.g. N/A
-
-When you finish creating your project page, make sure you add it into the appropriate navigation sections in the [mkdocs.yml](https://github.com/nhsengland/datascience/blob/main/mkdocs.yml) for website navigation purposes!
-
-[comment]: <> (The below header stops the title from being rendered (as mkdocs adds it to the page from the "title" attribute) - this way we can add it in the main.html, along with the summary.)
\ No newline at end of file
+[comment]: <> (The below header stops the title from being rendered (as mkdocs adds it to the page from the "title" attribute) - this way we can add it in the main.html, along with the summary.)
+#
\ No newline at end of file