This is an automated email from the ASF dual-hosted git repository.
grobmeier pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/logging-chainsaw.git
The following commit(s) were added to refs/heads/master by this push:
new 2814620 removed unnecessary blank
2814620 is described below
commit 2814620ee830aa6d0a4e9666f2bbeb541eda715c
Author: Christian Grobmeier <[email protected]>
AuthorDate: Tue Sep 26 22:58:05 2023 +0200
removed unnecessary blank
---
src/site/apt/index.apt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/site/apt/index.apt b/src/site/apt/index.apt
index fc68ec4..97864d3 100644
--- a/src/site/apt/index.apt
+++ b/src/site/apt/index.apt
@@ -46,7 +46,7 @@ So what is it really?
Rather than rely on a combination of tail/grep/vi or equivalent to
view/query/trace-through
a huge trail of logging events, you can use Chainsaw.
- Chainsaw can read local and ssh-reachable regular text log files, as well
as log files formatted in Log4j's XMLLayout. Chainsaw can also
+ Chainsaw can read local and ssh-reachable regular text log files, as well
as log files formatted in Log4j's XMLLayout. Chainsaw can also
receive events over TCP and UDP, read events from a DB, and can process
events generated by java.util.logging.
