From 79e5aea5c6d2e09fd94cadf07101d8c50ac79500 Mon Sep 17 00:00:00 2001 From: Boris Pfahringer Date: Mon, 4 Nov 2024 01:46:06 +0100 Subject: [PATCH] docs: fix typo {windows => window}.performance.now (#105) --- src/lib.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/lib.rs b/src/lib.rs index b5aa80e..895f926 100644 --- a/src/lib.rs +++ b/src/lib.rs @@ -71,7 +71,7 @@ //! //! This library can be built for WASM targets, but in this case the resolution and accuracy of //! measurements can be limited by the WASM environment. In particular, when running on the -//! `wasm32-unknown-unknown` target in browsers, `quanta` will use [windows.performance.now] as a +//! `wasm32-unknown-unknown` target in browsers, `quanta` will use [window.performance.now] as a //! clock. This mean the accuracy is limited to milliseconds instead of the usual nanoseconds on //! other targets. When running within a WASI environment (target `wasm32-wasi`), the accuracy of //! the clock depends on the VM implementation. @@ -135,7 +135,7 @@ //! [mach_absolute_time]: https://developer.apple.com/documentation/kernel/1462446-mach_absolute_time //! [clock_gettime]: https://linux.die.net/man/3/clock_gettime //! [prost_types_timestamp]: https://docs.rs/prost-types/0.7.0/prost_types/struct.Timestamp.html -//! [windows.performance.now]: https://developer.mozilla.org/en-US/docs/Web/API/Performance/now +//! [window.performance.now]: https://developer.mozilla.org/en-US/docs/Web/API/Performance/now #![deny(missing_docs)] #![deny(clippy::all)] #![allow(clippy::must_use_candidate)]