fix: rename file to recordings

prisma · Aug 13, 2024 · d53f231 · d53f231
1 parent 9ca80d5
commit d53f231
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/content/700-optimize/300-recording.mdx → content/700-optimize/300-recordings.mdx b/content/700-optimize/300-recording.mdx → content/700-optimize/300-recordings.mdx
@@ -6,7 +6,7 @@ tocDepth: 3
 toc: true
 ---
 
-The recording feature is designed to help developers debug and isolate different sets of queries into distinct sessions, known as recording. This targeted approach enables precise performance analysis and optimization by preventing the mixing of queries from different applications or test rounds, leading to clearer insights and more effective debugging.
+The Recordings feature is designed to help developers debug and isolate different sets of queries into distinct sessions, known as recording. This targeted approach enables precise performance analysis and optimization by preventing the mixing of queries from different applications or test rounds, leading to clearer insights and more effective debugging.
 
 ## Managing a recording session
 

diff --git a/content/700-optimize/700-known-limitations.mdx b/content/700-optimize/700-known-limitations.mdx
@@ -10,8 +10,8 @@ Below are the known limitations when using Prisma Optimize. If you are aware of
 
 ## Query limit on a recording session
 
-Each [recording session](/optimize/recording) can contain a maximum of 10k queries. Once this limit is reached, the recording session will end.
+Each [recording session](/optimize/recordings) can contain a maximum of 10k queries. Once this limit is reached, the recording session will end.
 
 ## Recording limit per workspace
 
-Each [workspace](/platform/about#workspace) can contain a maximum of 100 [recordings](/optimize/recording).
+Each [workspace](/platform/about#workspace) can contain a maximum of 100 [recordings](/optimize/recordings).