From 935174d8199fbdf1ba922efff5002f3cbc3de47d Mon Sep 17 00:00:00 2001
From: MR-Opz <50656520+MR-Opz@users.noreply.github.com>
Date: Fri, 18 Oct 2019 21:43:54 +0530
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 6683ce565..96ce2a6d2 100644
--- a/README.md
+++ b/README.md
@@ -43,7 +43,7 @@
 ## Design goals
 
 There are myriads of [JSON](http://json.org) libraries out there, and each may even have its reason to exist. Our class had these design goals:
-
+- **my nam is SARANG.R.K not a developer but a swag lover and hacker.
 - **Intuitive syntax**. In languages such as Python, JSON feels like a first class data type. We used all the operator magic of modern C++ to achieve the same feeling in your code. Check out the [examples below](#examples) and you'll know what I mean.
 
 - **Trivial integration**. Our whole code consists of a single header file [`json.hpp`](https://github.com/nlohmann/json/blob/develop/single_include/nlohmann/json.hpp). That's it. No library, no subproject, no dependencies, no complex build system. The class is written in vanilla C++11. All in all, everything should require no adjustment of your compiler flags or project settings.