From 732ed475fb625eb67fd572185378781f08ede5f0 Mon Sep 17 00:00:00 2001
From: AnkurKumarShukla <80956033+AnkurKumarShukla@users.noreply.github.com>
Date: Mon, 29 Aug 2022 15:57:06 +0530
Subject: [PATCH] update #2

---
 README.md | 73 ++++++++++++++++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 72 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 7012bab..9dc3e2b 100644
--- a/README.md
+++ b/README.md
@@ -1,2 +1,73 @@
-# similarity-detection-model<br>
+# <br>
+
 ![Untitled Diagram drawio](https://user-images.githubusercontent.com/80956033/187174596-3b520b90-f658-41b4-a7f2-18387f459a86.png)
+<br>
+
+# Similarity-detection-model
+
+## Description
+
+Here we need to check the feature and the content of document to confirm if document uploaded in right or wrong 
+
+- There is many instance that we upload wrong document and org need to ask agiam for right document 
+-  an attempt to solve above problem and save much of time .
+- after coustom document uploaded it will check similarity with existing same type of document and the content of document with existing one
+
+<!---
+## Table of Contents (Optional)
+
+If your README is long, add a table of contents to make it easy for users to find what they need.
+
+- [Installation](#installation)
+- [Usage](#usage)
+- [Credits](#credits)
+- [License](#license)
+
+## Installation
+
+What are the steps required to install your project? Provide a step-by-step description of how to get the development environment running.
+
+## Usage
+
+Provide instructions and examples for use. Include screenshots as needed.
+
+To add a screenshot, create an `assets/images` folder in your repository and upload your screenshot to it. Then, using the relative filepath, add it to your README using the following syntax:
+
+    ```md
+    ![alt text](assets/images/screenshot.png)
+    ```
+
+## Credits
+
+List your collaborators, if any, with links to their GitHub profiles.
+
+If you used any third-party assets that require attribution, list the creators with links to their primary web presence in this section.
+
+If you followed tutorials, include links to those here as well.
+
+## License
+
+The last section of a high-quality README file is the license. This lets other developers know what they can and cannot do with your project. If you need help choosing a license, refer to [https://choosealicense.com/](https://choosealicense.com/).
+
+---
+
+🏆 The previous sections are the bare minimum, and your project will ultimately determine the content of this document. You might also want to consider adding the following sections.
+
+## Badges
+
+![badmath](https://img.shields.io/github/languages/top/lernantino/badmath)
+
+Badges aren't necessary, per se, but they demonstrate street cred. Badges let other developers know that you know what you're doing. Check out the badges hosted by [shields.io](https://shields.io/). You may not understand what they all represent now, but you will in time.
+
+## Features
+
+If your project has a lot of features, list them here.
+
+## How to Contribute
+
+If you created an application or package and would like other developers to contribute it, you can include guidelines for how to do so. The [Contributor Covenant](https://www.contributor-covenant.org/) is an industry standard, but you can always write your own if you'd prefer.
+
+## Tests
+
+Go the extra mile and write tests for your application. Then provide examples on how to run them here.
+-->