From 8cc4ad4d80d91d4074a079bd206752b7ad6086a6 Mon Sep 17 00:00:00 2001 From: Wahid Khan Date: Mon, 20 Feb 2023 11:43:21 +0530 Subject: [PATCH] website: fix typos (#258) --- website/docs/guide/how-to-integrate-for-non-gki.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/guide/how-to-integrate-for-non-gki.md b/website/docs/guide/how-to-integrate-for-non-gki.md index 273882ff..9964dd68 100644 --- a/website/docs/guide/how-to-integrate-for-non-gki.md +++ b/website/docs/guide/how-to-integrate-for-non-gki.md @@ -37,7 +37,7 @@ But if you encounter a boot loop when integrated KernelSU, it is maybe *kprobe i :::tip How to check if kprobe is broken？ -comment out `ksu_enable_sucompat()` and `ksu_enable_ksud()` in `KernelSU/kernel/ksu.c`, the the device boot normally, then kprobe may be broken. +comment out `ksu_enable_sucompat()` and `ksu_enable_ksud()` in `KernelSU/kernel/ksu.c`, if the device boots normally, then kprobe may be broken. ::: ## Manully modify the kernel source