fix: corrected types.Part.from_data with types.Part.from_bytes in docs/artifacts/index.md (#259)

Co-authored-by: Lavi Nigam <[email protected]>

Author: yrangana

docs/artifacts/index.md

@@ -31,7 +31,7 @@ In ADK, **Artifacts** represent a crucial mechanism for managing named, versione
     )
 
     # You can also use the convenience constructor:
-    # image_artifact_alt = types.Part.from_data(data=image_bytes, mime_type="image/png")
+    # image_artifact_alt = types.Part.from_bytes(data=image_bytes, mime_type="image/png")
 
     print(f"Artifact MIME Type: {image_artifact.inline_data.mime_type}")
     print(f"Artifact Data (first 10 bytes): {image_artifact.inline_data.data[:10]}...")
@@ -174,7 +174,6 @@ Understanding artifacts involves grasping a few key components: the service that
     * `data` (`bytes`): The raw binary content of the artifact.  
     * `mime_type` (`str`): A standard MIME type string (e.g., `'application/pdf'`, `'image/png'`, `'audio/mpeg'`) describing the nature of the binary data. **This is crucial for correct interpretation when loading the artifact.**
 
-
 === "Python"
 
     ```python
@@ -190,11 +189,11 @@ Understanding artifacts involves grasping a few key components: the service that
     )
 
     # Using the convenience class method (equivalent)
-    pdf_artifact_alt_py = types.Part.from_data(data=pdf_bytes, mime_type=pdf_mime_type)
+    pdf_artifact_alt_py = types.Part.from_bytes(data=pdf_bytes, mime_type=pdf_mime_type)
 
     print(f"Created Python artifact with MIME type: {pdf_artifact_py.inline_data.mime_type}")
     ```
-
+    
 === "Java"
 
     ```java
@@ -767,4 +766,4 @@ To use artifacts effectively and maintainably:
 * **Cleanup Strategy:** For persistent storage like `GcsArtifactService`, artifacts remain until explicitly deleted. If artifacts represent temporary data or have a limited lifespan, implement a strategy for cleanup. This might involve:  
     * Using GCS lifecycle policies on the bucket.  
     * Building specific tools or administrative functions that utilize the `artifact_service.delete_artifact` method (note: delete is *not* exposed via context objects for safety).  
-    * Carefully managing filenames to allow pattern-based deletion if needed.
+    * Carefully managing filenames to allow pattern-based deletion if needed.