From 8a97aad021b16eb72591323691e902b06bd54087 Mon Sep 17 00:00:00 2001 From: wu-sheng Date: Mon, 25 Dec 2017 15:16:06 +0800 Subject: [PATCH] Fix a comment word. --- .../apm/agent/core/plugin/match/ProtectiveShieldMatcher.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apm-sniffer/apm-agent-core/src/main/java/org/apache/skywalking/apm/agent/core/plugin/match/ProtectiveShieldMatcher.java b/apm-sniffer/apm-agent-core/src/main/java/org/apache/skywalking/apm/agent/core/plugin/match/ProtectiveShieldMatcher.java index d1c80a663..a4c702765 100644 --- a/apm-sniffer/apm-agent-core/src/main/java/org/apache/skywalking/apm/agent/core/plugin/match/ProtectiveShieldMatcher.java +++ b/apm-sniffer/apm-agent-core/src/main/java/org/apache/skywalking/apm/agent/core/plugin/match/ProtectiveShieldMatcher.java @@ -22,7 +22,7 @@ import org.apache.skywalking.apm.agent.core.logging.api.ILog; import org.apache.skywalking.apm.agent.core.logging.api.LogManager; /** - * In same cases, some frameworks and libraries use some binary codes tech too. From the community feedback, some of + * In some cases, some frameworks and libraries use some binary codes tech too. From the community feedback, some of * them have compatible issues with byte-buddy core, which trigger "Can't resolve type description" exception. * * So I build this protective shield by a nested matcher. When the origin matcher(s) can't resolve the type, the