Update reference in docs from done to release (#3211)

weslord · web-flow · commit 81e2ff05247c · 2024-05-15T17:04:16.000-05:00
diff --git a/docs/pages/guides/project-structure.md b/docs/pages/guides/project-structure.md
@@ -94,7 +94,7 @@ export const getClient = () => {
 }
 ```
 
-Okay. Great - the simplest thing that could possibly work. It seems like one of our routes that checks out a client to run a transaction is forgetting to call `done` in some situation! Oh no! We are leaking a client & have hundreds of these routes to go audit. Good thing we have all our client access going through this single file. Lets add some deeper diagnostic information here to help us track down where the client leak is happening.
+Okay. Great - the simplest thing that could possibly work. It seems like one of our routes that checks out a client to run a transaction is forgetting to call `release` in some situation! Oh no! We are leaking a client & have hundreds of these routes to go audit. Good thing we have all our client access going through this single file. Lets add some deeper diagnostic information here to help us track down where the client leak is happening.
 
 ```js
 export const query = async (text, params) => {

Original file line number	Diff line number	Diff line change
`@@ -94,7 +94,7 @@ export const getClient = () => {`
`94`	`94`	`}`
`95`	`95`	```
`96`	`96`
`97`		-Okay. Great - the simplest thing that could possibly work. It seems like one of our routes that checks out a client to run a transaction is forgetting to call `done` in some situation! Oh no! We are leaking a client & have hundreds of these routes to go audit. Good thing we have all our client access going through this single file. Lets add some deeper diagnostic information here to help us track down where the client leak is happening.
	`97`	+Okay. Great - the simplest thing that could possibly work. It seems like one of our routes that checks out a client to run a transaction is forgetting to call `release` in some situation! Oh no! We are leaking a client & have hundreds of these routes to go audit. Good thing we have all our client access going through this single file. Lets add some deeper diagnostic information here to help us track down where the client leak is happening.
`98`	`98`
`99`	`99`	```js
`100`	`100`	`export const query = async (text, params) => {`