From f19ed5a72752a250759f5a0024b817a2b52147de Mon Sep 17 00:00:00 2001
From: Jiacheng Xu <xjcmaxwellcjx@gmail.com>
Date: Tue, 12 Sep 2023 18:27:51 +0800
Subject: [PATCH] update

---
 .github/workflows/build-docs.yml |  9 +++++++++
 .gitignore                       |  3 ++-
 Makefile                         |  1 +
 README.md                        | 10 +++-------
 docs/index.md                    |  6 ++----
 5 files changed, 17 insertions(+), 12 deletions(-)

diff --git a/.github/workflows/build-docs.yml b/.github/workflows/build-docs.yml
index b1b9c3b..18e9001 100644
--- a/.github/workflows/build-docs.yml
+++ b/.github/workflows/build-docs.yml
@@ -10,6 +10,15 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v3
+      - uses: actions/setup-go@v4
+        with:
+          go-version: 1.20
+      - name: Generate Docs
+        run: make generate-docs
+      - name: Check nothing has changed
+        run: |
+          set -xo pipefail
+          git diff --exit-code -- .
       - uses: actions/setup-python@v4
         with:
           python-version: 3.x
diff --git a/.gitignore b/.gitignore
index 3370316..a9c4103 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,4 @@
 dist
 .idea
-.DS_Store
\ No newline at end of file
+.DS_Store
+site
\ No newline at end of file
diff --git a/Makefile b/Makefile
index f705060..15aabba 100644
--- a/Makefile
+++ b/Makefile
@@ -1,5 +1,6 @@
 .PHONY: generate-docs
 generate-docs:
 	@cp README.md docs/index.md
+	@sed -i '' 's/\.\/CONTRIBUTING\.md/contributing\.md/g' docs/index.md
 	@cp CONTRIBUTING.md docs/contributing.md
 	@go run hack/gendocs/main.go
\ No newline at end of file
diff --git a/README.md b/README.md
index 80144c4..1a4504b 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,6 @@
-# Token Security Benchmark (TSB)
+# Token Security Benchmark
 
-The `token-security-benchmark` is a comprehensive repository aimed at identifying and cataloging scams like honeypots, and intentional backdoors that may be present in token smart contracts within the crypto ecosystem. This benchmark serves as:
+Token Security Benchmark(TSB) aims at identifying and cataloging scams like honeypots, and intentional backdoors that may be present in token smart contracts within the crypto ecosystem. This benchmark serves as:
 
 - **A Shield against Malicious Contracts:** By showcasing a defined list of malicious token contract patterns, it empowers users and project teams to recognize and steer clear of contracts with hidden intents, thereby ensuring safer interactions within the decentralized space.
 
@@ -15,14 +15,10 @@ The `token-security-benchmark` is a comprehensive repository aimed at identifyin
 - **Descriptions:** Each pattern is thoroughly dissected, detailing its operation, potential consequences, and techniques for avoidance.
 - **Real-world Samples:** For each pattern, contract samples that exemplify the described malicious intent are provided, forming a practical point of reference.
 
-## How to Contribute
+## Contribute
 
 Maintaining the relevance and comprehensiveness of this repository is a joint endeavor. We earnestly welcome community contributions. For details on how to contribute, kindly refer to our [Contribution Guidelines](./CONTRIBUTING.md).
 
 ## Acknowledgments
 
 Our profound gratitude to all developers, researchers, and crypto enthusiasts who have been instrumental in shaping this repository. We hope to collaboratively fortify crypto user security and invite everyone to join this collective endeavor.
-
-## License
-
-This repository is distributed under the Apache License, Version 2.0. For more specifics, please review our [LICENSE](./LICENSE) file.
\ No newline at end of file
diff --git a/docs/index.md b/docs/index.md
index fa1011f..3b2fec0 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -3,7 +3,7 @@
 The `token-security-benchmark` is a comprehensive repository aimed at identifying and cataloging scams like honeypots, and intentional backdoors that may be present in token smart contracts within the crypto ecosystem. This benchmark serves as:
 
 - **A Shield against Malicious Contracts:** By showcasing a defined list of malicious token contract patterns, it empowers users and project teams to recognize and steer clear of contracts with hidden intents, thereby ensuring safer interactions within the decentralized space.
- 
+
 - **A Testing Ground for Developers:** With a clear classification of malicious patterns and real-world examples, developers creating tools to detect these malicious token smart contracts can effectively evaluate their systems against a standardized benchmark.
 
 - **A Catalyst for Research:** By elucidating the deceitful practices adopted in token smart contracts, we aspire to drive more research towards crypto user safety, encouraging the community to devise strategies that deter such behaviors.
@@ -17,12 +17,10 @@ The `token-security-benchmark` is a comprehensive repository aimed at identifyin
 
 ## How to Contribute
 
-Maintaining the relevance and comprehensiveness of this repository is a joint endeavor. We earnestly welcome community contributions. For details on how to contribute, kindly refer to our [Contribution Guidelines](./CONTRIBUTING.md).
+Maintaining the relevance and comprehensiveness of this repository is a joint endeavor. We earnestly welcome community contributions. For details on how to contribute, kindly refer to our [Contribution Guidelines](contributing.md).
 
 ## Acknowledgments
 
 Our profound gratitude to all developers, researchers, and crypto enthusiasts who have been instrumental in shaping this repository. We hope to collaboratively fortify crypto user security and invite everyone to join this collective endeavor.
 
 ## License
-
-This repository is distributed under the Apache License, Version 2.0. For more specifics, please review our [LICENSE](./LICENSE) file.
\ No newline at end of file