From 9d0673af0aebb461188e61d690c83c576c9408f5 Mon Sep 17 00:00:00 2001 From: amit2103 Date: Fri, 9 Oct 2015 23:20:58 +0530 Subject: [PATCH] Made changes according to feedback issue #258 --- monostate/index.md | 2 +- monostate/src/main/java/com/iluwatar/monostate/Request.java | 1 - 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/monostate/index.md b/monostate/index.md index 369d24ff8..2b88f131e 100644 --- a/monostate/index.md +++ b/monostate/index.md @@ -14,7 +14,7 @@ tags: Java **Applicability:** Use the Monostate pattern when * The same state must be shared across all instances of a class. -* Typically this pattern might be used everywhere a SingleTon might be used. Singleton usage however is not transparent, Monostate usage is. +* Typically this pattern might be used everywhere a Singleton might be used. Singleton usage however is not transparent, Monostate usage is. * Monostate has one major advantage over singleton. The subclasses might decorate the shared state as they wish and hence can provide dynamically different behaviour than the base class. **Typical Use Case:** diff --git a/monostate/src/main/java/com/iluwatar/monostate/Request.java b/monostate/src/main/java/com/iluwatar/monostate/Request.java index 037ab96aa..ee1f31d85 100644 --- a/monostate/src/main/java/com/iluwatar/monostate/Request.java +++ b/monostate/src/main/java/com/iluwatar/monostate/Request.java @@ -10,7 +10,6 @@ public class Request { public final String value; public Request(String value) { - super(); this.value = value; } }