diff --git a/packages/console/src/assets/docs/guides/web-php/README.mdx b/packages/console/src/assets/docs/guides/web-php/README.mdx
index 21c13c289..a798f3676 100644
--- a/packages/console/src/assets/docs/guides/web-php/README.mdx
+++ b/packages/console/src/assets/docs/guides/web-php/README.mdx
@@ -147,7 +147,7 @@ To clean up the Python session and Logto session, we can designate a post sign-o
 And a sign-out route can be implemented as follows:
 
 <pre>
-  <code className="language-python">
+  <code className="language-php">
 {`Route::get('/sign-out', function () {
   return redirect(
     // Redirect the user to the home page after a successful sign-out
diff --git a/packages/console/src/assets/docs/guides/web-python/README.mdx b/packages/console/src/assets/docs/guides/web-python/README.mdx
index 1ff886610..5b84fd154 100644
--- a/packages/console/src/assets/docs/guides/web-python/README.mdx
+++ b/packages/console/src/assets/docs/guides/web-python/README.mdx
@@ -199,6 +199,8 @@ Now, you can test your application:
 Now, you have a working sign-in flow, but your routes are still unprotected. Per the framework you use, you can create a decorator such as `@authenticated` to protect your routes. For example:
 
 ```python
+from functools import wraps
+
 def authenticated(func):
     @wraps(func)
     async def wrapper(*args, **kwargs):