From a7cf0d473e9e54af21b3ae87b86fe878d7fb07a5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Raoul=20Luqu=C3=A9?=
 <125205120+RaoulLuque@users.noreply.github.com>
Date: Wed, 17 Sep 2025 10:56:00 +0200
Subject: [PATCH] Fix typo in README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index bc263975..1f982ae9 100644
--- a/README.md
+++ b/README.md
@@ -124,7 +124,7 @@ let svg_string = plot.to_svg(800, 600, 1.0)?;
 
 The above example uses the legacy API that is backwards compatible with the Kaleido API. However, for more efficient workflows a `StaticExporter` object can be built and reused between calls to `write_image`. 
 
-More specificallt, enabling any of the `plotly` features `static_export_chromedriver`, `static_export_geckodriver`, or `static_export_default` gives access to both the synchronous `StaticExporter` and the asynchronous `AsyncStaticExporter` (available via `plotly::plotly_static`). For exporter reuse and up-to-date sync/async usage patterns, please see the dedicated example in `examples/static_export`, which demonstrates both synchronous and asynchronous exporters and how to reuse a single exporter instance across multiple exports.
+More specifically, enabling any of the `plotly` features `static_export_chromedriver`, `static_export_geckodriver`, or `static_export_default` gives access to both the synchronous `StaticExporter` and the asynchronous `AsyncStaticExporter` (available via `plotly::plotly_static`). For exporter reuse and up-to-date sync/async usage patterns, please see the dedicated example in `examples/static_export`, which demonstrates both synchronous and asynchronous exporters and how to reuse a single exporter instance across multiple exports.
 
  For further details see [`plotly_static` crate documentation](https://docs.rs/plotly_static/).