From e107970f4f6eda8d28ef29dadc33a4b2cc6e15a4 Mon Sep 17 00:00:00 2001
From: race <96184147+raacee@users.noreply.github.com>
Date: Thu, 19 Oct 2023 22:49:49 +0200
Subject: [PATCH] corrected typo in polymorphism section

---
 site/en/guide/intro_to_graphs.ipynb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/en/guide/intro_to_graphs.ipynb b/site/en/guide/intro_to_graphs.ipynb
index 153cc24d469..0392a160d55 100644
--- a/site/en/guide/intro_to_graphs.ipynb
+++ b/site/en/guide/intro_to_graphs.ipynb
@@ -340,7 +340,7 @@
       "source": [
         "### Polymorphism: one `Function`, many graphs\n",
         "\n",
-        "A `tf.Graph` is specialized to a specific type of inputs (for example, tensors with a specific [`dtype`](https://www.tensorflow.org/api_docs/python/tf/dtypes/DType) or objects with the same [`id()`](https://docs.python.org/3/library/functions.html#id])).\n",
+        "A `tf.Graph` is specialized to a specific type of inputs (for example, tensors with a specific [`dtype`](https://www.tensorflow.org/api_docs/python/tf/dtypes/DType) or objects with the same [`id()`](https://docs.python.org/3/library/functions.html#id)).\n",
         "\n",
         "Each time you invoke a `Function` with a set of arguments that can't be handled by any of its existing graphs (such as arguments with new `dtypes` or incompatible shapes), `Function` creates a new `tf.Graph` specialized to those new arguments. The type specification of a `tf.Graph`'s inputs is known as its **input signature** or just a **signature**. For more information regarding when a new `tf.Graph` is generated and how that can be controlled, go to the _Rules of tracing_ section of the [Better performance with `tf.function`](./function.ipynb) guide.\n",
         "\n",