Update READMEs

README.md

@@ -3,15 +3,14 @@
 [![Discord](https://img.shields.io/discord/916955582181822486?label=Discord&color=blue&logo=discord&logoColor=white)](https://discord.gg/vh8NCgdp8J)
 ![Codespace Supported](https://img.shields.io/badge/Codespace_Supported-000000?style=flat&logo=github)
 
-Judger is supposed to be a simple **sandbox service** which works for online-judge systems.
+Library & application which supports running code in a sandboxed environment.
 
-## System
+## System Prerequisite
 
 Judger currently use `nix` to make necessary system invoke like `fork()`.
 So you might need to check whether you are using the supported system from the main-page of [nix](https://github.com/nix-rust/nix).
 
 **Briefly speaking, judger-rs is now supposing you are decided to run it on linux.**
-We'll consider other platform, but in a lower priority.
 
 ## Development
 
@@ -28,9 +27,9 @@ There is a setup script to help you quickly get ready.
 ./scripts/env_setup.bash
 ```
 
-## Contribute
+### Debugging
 
-We have a guide in judger's [WIKI](https://github.com/OJ-lab/judger/wiki/Contribution-Guide)
+Launch settings are already configured in `.vscode/launch.json`, try in the debug panel.
 
 ## Deeper Docs
 

judge-core/README.md

@@ -11,8 +11,6 @@ See what we've got (or plan to do) currently:
 - a **sandbox** mainly based on `rlimit` and `seccomp`, helps you to spawn process safely
 - a **monitor** (or judger) with sandboxes,
 enables you to run single part of judge test_case (if you got everything needed for judge)
-- a **judge_builder** (WIP) to provide a higher level interface to start a judge,
-supposing the judge directory structure is following [ICPC Problem Package format](https://icpc.io/problem-package-format/examples/directory_structure)
 
 ## Use strace for seccomp withlist dev