修改文档

Author: FlyJingFish

docs/AndroidAopReplaceClass.md

@@ -9,7 +9,9 @@ This aspect is used to replace the method call in the code, and needs to be used
 - **_The advantage of this method is that it can "equivalently" monitor the call of certain system methods (code in android.jar), and the first two do not have this feature, so if it is not based on this requirement, it is recommended to use [@AndroidAopMatchClassMethod](https://flyjingfish.github.io/AndroidAOP/AndroidAopMatchClassMethod/)_**
 
 !!! note
-    <li>To sum up, this function can be said to be a supplement to [@AndroidAopMatchClassMethod](https://flyjingfish.github.io/AndroidAOP/AndroidAopMatchClassMethod/) (the code in android.jar cannot be woven into AOP code). The reason why [ProceedJoinPoint](https://flyjingfish.github.io/AndroidAOP/ProceedJoinPoint/) is not used is that this method may be restricted by different versions of Android. It can neither use reflection to call the original method nor weave in AOP code, so it cannot be encapsulated with [ProceedJoinPoint](/AndroidAOP/ProceedJoinPoint/). If you really want to use it, it is recommended to use [MatchClassMethodProxy](#4-proxy-usage-of-androidaopmatchclassmethod) </li><br> <li><strong>After you modify the configuration of this aspect, you should clean the project before continuing development</strong></li>
+    <li>To sum up, this function can be said to be a supplement to [@AndroidAopMatchClassMethod](https://flyjingfish.github.io/AndroidAOP/AndroidAopMatchClassMethod/) (the code in android.jar cannot be woven into AOP code). The reason why [ProceedJoinPoint](https://flyjingfish.github.io/AndroidAOP/ProceedJoinPoint/) is not used is that this method may be restricted by different versions of Android. It can neither use reflection to call the original method nor weave in AOP code, so it cannot be encapsulated with [ProceedJoinPoint](/AndroidAOP/ProceedJoinPoint/). If you really want to use it, it is recommended to use [MatchClassMethodProxy](#4-proxy-usage-of-androidaopmatchclassmethod) </li><br>
+    <li>Although some system methods can be hooked, in the final analysis, they are calls within the hook installation package, not including calls at the framework layer</li><br>
+    <li><strong>After you modify the configuration of this aspect, you should clean the project before continuing development</strong></li>
 
 ## 1. Description
 

docs/zh/AndroidAopReplaceClass.md

@@ -8,7 +8,9 @@
 
 
 !!! note
-    <li>综上所述这个功能可以说是[@AndroidAopMatchClassMethod](/AndroidAOP/zh/AndroidAopMatchClassMethod)的一种补充（android.jar里的代码无法织入AOP代码），之所以不使用[ProceedJoinPoint](/AndroidAOP/zh/ProceedJoinPoint)也是因为这种方法可能受到Android不同版本的限制，既不可以使用反射来调用原方法，也不可以织入AOP代码，所以就不可以去用[ProceedJoinPoint](/AndroidAOP/zh/ProceedJoinPoint)封装了，如果实在想用，建议使用 [MatchClassMethodProxy](#4androidaopmatchclassmethod) </li><br> <li><strong>当你修改这个切面的相关配置后你应该clean项目后再继续开发</strong></li>
+    <li>综上所述这个功能可以说是[@AndroidAopMatchClassMethod](/AndroidAOP/zh/AndroidAopMatchClassMethod)的一种补充（android.jar里的代码无法织入AOP代码），之所以不使用[ProceedJoinPoint](/AndroidAOP/zh/ProceedJoinPoint)也是因为这种方法可能受到Android不同版本的限制，既不可以使用反射来调用原方法，也不可以织入AOP代码，所以就不可以去用[ProceedJoinPoint](/AndroidAOP/zh/ProceedJoinPoint)封装了，如果实在想用，建议使用 [MatchClassMethodProxy](#4androidaopmatchclassmethod) </li><br>
+    <li>虽然可以hook一些系统方法，但归根到底他是hook的安装包内部的调用，不包括framework层的调用</li><br>
+    <li><strong>当你修改这个切面的相关配置后你应该clean项目后再继续开发</strong></li>
 
 
 ## 一、说明