middleware deleted

Author: aidankmcalister

content/200-orm/200-prisma-client/100-queries/100-query-optimization-performance.mdx

@@ -42,8 +42,6 @@ To get started, follow the [integration guide](/optimize/getting-started) and ad
 
 You can also [log query events at the client level](/orm/prisma-client/observability-and-logging/logging#event-based-logging) to view the generated queries, their parameters, and execution times.
 
-If you are particularly focused on monitoring query duration, consider using [logging middleware](/orm/prisma-client/client-extensions/middleware/logging-middleware).
-
 :::
 
 ## Using bulk queries

content/200-orm/200-prisma-client/300-client-extensions/500-middleware/100-soft-delete-middleware.mdx

@@ -230,32 +230,6 @@ The `Prisma.Result` type utility is used to infer the type of the extended `User
 
 ## Limitations
 
-### Usage of `$on` and `$use` with extended clients
-
-`$on` and `$use` are not available in extended clients. If you would like to continue using these [client-level methods](/orm/reference/prisma-client-reference#client-methods) with an extended client, you will need to hook them up before extending the client.
-
-```ts
-const prisma = new PrismaClient()
-
-prisma.$use(async (params, next) => {
-  console.log('This is middleware!')
-  return next(params)
-})
-
-const xPrisma = prisma.$extends({
-  name: 'myExtension',
-  model: {
-    user: {
-      async signUp(email: string) {
-        await prisma.user.create({ data: { email } })
-      },
-    },
-  },
-})
-```
-
-To learn more, see our documentation on [`$on`](/orm/reference/prisma-client-reference#on) and [`$use`](/orm/reference/prisma-client-reference#use)
-
 ### Usage of client-level methods in extended clients
 
 [Client-level methods](/orm/reference/prisma-client-reference#client-methods) do not necessarily exist on extended clients. For these clients you will need to first check for existence before using.