From c5aa1a0c6936358e02e254f91c62a971e5716009 Mon Sep 17 00:00:00 2001 From: Andreas Schildbach Date: Sun, 28 Apr 2019 13:44:38 +0200 Subject: [PATCH] Fix unbalanced

tags in JavaDocs. --- core/src/main/java/org/bitcoinj/core/AlertMessage.java | 2 +- .../java/org/bitcoinj/store/LevelDBFullPrunedBlockStore.java | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/core/src/main/java/org/bitcoinj/core/AlertMessage.java b/core/src/main/java/org/bitcoinj/core/AlertMessage.java index 5020d5c2..b4e11312 100644 --- a/core/src/main/java/org/bitcoinj/core/AlertMessage.java +++ b/core/src/main/java/org/bitcoinj/core/AlertMessage.java @@ -31,7 +31,7 @@ import java.util.Set; * log, email), or if you decide to use alerts for notifications that are specific to your app in some way, to parse it. * For example, you could treat it as an upgrade notification specific to your app. Satoshi designed alerts to ensure * that software upgrades could be distributed independently of a hard-coded website, in order to allow everything to - * be purely peer-to-peer. You don't have to use this of course, and indeed it often makes more sense not to.

+ * be purely peer-to-peer. You don't have to use this of course, and indeed it often makes more sense not to.

* *

Before doing anything with an alert, you should check {@link AlertMessage#isSignatureValid()}.

* diff --git a/core/src/main/java/org/bitcoinj/store/LevelDBFullPrunedBlockStore.java b/core/src/main/java/org/bitcoinj/store/LevelDBFullPrunedBlockStore.java index b026b681..814f9538 100644 --- a/core/src/main/java/org/bitcoinj/store/LevelDBFullPrunedBlockStore.java +++ b/core/src/main/java/org/bitcoinj/store/LevelDBFullPrunedBlockStore.java @@ -56,7 +56,7 @@ import com.google.common.collect.Lists; /** *

* An implementation of a Fully Pruned Block Store using a leveldb implementation as the backing data store. - *

+ *

* *

* Includes number of caches to optimise the initial blockchain download.