Skip to content

Commit 66c91aa

Browse files
authored
docs: small formatting fixes
1 parent cb2ba95 commit 66c91aa

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

src/lib.rs

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -255,13 +255,15 @@
255255
//! ```bash
256256
//! RUSTFLAGS="-l framework=WebKit" cargo build --target=x86_64-apple-darwin --release
257257
//! ```
258+
//!
258259
//! ### Windows
259260
//!
260261
//! WebView2 provided by Microsoft Edge Chromium is used. So wry supports Windows 7, 8, 10 and 11.
261262
//!
262263
//! ### Android
263264
//!
264265
//! In order for `wry` to be able to create webviews on Android, there are a few requirements that your application needs to uphold:
266+
//!
265267
//! 1. You need to set a few environment variables that will be used to generate the necessary kotlin
266268
//! files that you need to include in your Android application for wry to function properly.
267269
//! - `WRY_ANDROID_PACKAGE`: which is the reversed domain name of your android project and the app name in snake_case, for example, `com.wry.example.wry_app`
@@ -271,7 +273,7 @@
271273
//! 3. Your Rust app needs to call `wry::android_setup` function to setup the necessary logic to be able to create webviews later on.
272274
//! 4. Your Rust app needs to call `wry::android_binding!` macro to setup the JNI functions that will be called by `WryActivity` and various other places.
273275
//!
274-
//! It is recommended to use [`tao`](https://docs.rs/tao/latest/tao/) crate as it provides maximum compatibility with `wry`
276+
//! It is recommended to use the [`tao`](https://docs.rs/tao/latest/tao/) crate as it provides maximum compatibility with `wry`.
275277
//!
276278
//! ```
277279
//! #[cfg(target_os = "android")]

0 commit comments

Comments
 (0)