Merge pull request #131 from julelang/docs/wording

docs(readme): improve the wording and contextual structure

README.md

@@ -6,61 +6,56 @@
 
 An effective programming language to build efficient, fast, reliable and safe software while maintaining simplicity.
 
-This repository is the main source tree of the Jule. \
-It contains the reference compiler, API, and standard library.
+This repository is the main source tree of Jule. \
+It contains the reference compiler, API, and the standard library.
 
 [Website](https://jule.dev) |
 [Manual](https://manual.jule.dev) |
 [Future of Jule](https://jule.dev/future-of-jule) |
 [Contributing](https://jule.dev/contribute) |
 [Community](https://jule.dev/community)
 
-</strong>
-
 </div>
 
 ### Key Features
 
 - Optimized for fast and safe programs
-- Empowered compile-time: reflection, evaluation, matching, and more by the standard comptime library
+- Empowered compile-time: reflection, evaluation, matching, and more
 - Deterministic memory management with reference-counting and smart pointers
-- [Easy cross compilation](https://manual.jule.dev/compiler/cross-compilation): generate IR for target platform and imitate the target architecture
-- Cross platform implemented standard library
-- Built-in support to write tests
-- Built-in [concurrency](https://manual.jule.dev/concurrency/): easy to use managed threads, channels, mutexes, condition variables and more
-- Easy error-handling with [exceptionals](https://manual.jule.dev/error-handling/exceptionals), very like optional types
-- Easy low-level programming
-- High [interoperability](https://manual.jule.dev/integrated-jule/interoperability/) with C, C++, Objective-C and Objective-C++
-- Disable variable shadowing by default, immutability by default, boundary checking, no uninitialized memory
-- The [API](https://manual.jule.dev/api/) written in Jule and C++ and allows extend Jule with C++ thanks to interoperability
+- Default immutability, boundary checking, no uninitialized memory, variable shadowing disabled
+- Built-in testing framework
+- Easy low-level development
+- [Easy cross compilation](https://manual.jule.dev/compiler/cross-compilation): standard library support, target platform IR generation and architecture imitation
+- Easy error-handling with [exceptionals](https://manual.jule.dev/error-handling/exceptionals), much like optional types
+- [Concurrency support](https://manual.jule.dev/concurrency): managed threads, channels, mutexes, condition variables, and more
+- High [interoperability](https://manual.jule.dev/integrated-jule/interoperability) with C, C++, Objective-C and Objective-C++
+- C++ [API](https://manual.jule.dev/api) for extending Jule with interoperability
 
 > [!IMPORTANT]
-> Jule does not have a stable version yet and is still being developed to become more stable.
+> Jule does not have a stable version yet and is still becoming more stable with each commit.
 > Some commits may not be fully honored due to some compiler/API errors.
-> Please report it with the [Jule Issue Tracker](https://github.com/julelang/jule/issues) if you come across something like this.
-> You can also [join the Discord community](https://discord.gg/XNSUUDuGGQ) to discuss, helping, and ask more questions about Jule with the community.
-
+> Please report any issues you may encounter with the [Jule Issue Tracker](https://github.com/julelang/jule/issues).
+> You can also [join the Discord community](https://discord.gg/XNSUUDuGGQ) to discuss, help, and ask more questions about Jule.
 
 ## Community
 
 Contribute and get involved in our community.
 
-Join Julenours to support Jule, explore and interact with the community.\
+Join Julenours to support Jule, explore, and interact with the community. \
 Our main community platforms:
 
-- [Official Discord Server of The Jule Community](https://discord.gg/XNSUUDuGGQ)
+- [Official Discord Server](https://discord.gg/XNSUUDuGGQ)
 - [GitHub Discussions](https://github.com/jule-lang/jule/discussions)
 
 ## Build from Source
 
 If you want to get Jule from the source, there are many ways to do so.
-Jule has a bootstrapped compiler, so you'll need to get one first if you don't have one.
-There are two options to do this: obtain the release or use IR.
-However, it is recommended to use IR as it is always more up to date and ensures there is enough left to compile the [master](https://github.com/julelang/jule/tree/master) branch.
-Officially, the recommended method to always get the most up-to-date build of compiler from the latest source code is to use IR.
+Jule has a bootstrapped compiler, so you'll need to have a working one first.
+There are two options to do this: obtain a binary from the [releases](https://github.com/julelang/jule/releases) or use the [official IR](https://github.com/julelang/julec-ir).
+However, it is recommended to use IR as it is always up to date and ensures [master](https://github.com/julelang/jule/tree/master) branch compatibility.
 
-If you already have a compiler, you can use build scripts designed for developers by obtaining the latest source code.
-But remember, these are for developers and they compile the compiler for debugging new source code, not for production use. So you can get an inefficient and slow version.
+If you already have a compiler, you can use build scripts designed for developers to compile JuleC.
+Remember, these are meant for developers, not for production use. They compile the compiler for debugging new source code.
 
 - Learn about: [compile from IR](https://manual.jule.dev/getting-started/installation/compiling-from-source/compile-from-ir)
 - Learn about: [build scripts](https://manual.jule.dev/getting-started/installation/compiling-from-source/build-scripts)
@@ -69,14 +64,11 @@ But remember, these are for developers and they compile the compiler for debuggi
 
 Any contribution to Jule is greatly appreciated, whether it's a typo fix, a brand new compiler feature, or a bug report.
 
-The Jule project only uses issues for things like proposals, bug reports, and vulnerabilities.
-If you want to discuss anything, [discussions](https://github.com/julelang/jule/discussions) is a better place for that.
-If you are interested in reporting a security vulnerability, please read the out [security policy](https://github.com/julelang/jule/security/policy) first.
+The Jule project uses GitHub issues for things like proposals, bug reports, and security vulnerabilities.
+If you want to discuss anything, [discussions](https://github.com/julelang/jule/discussions) is a better place to do that.
+If you are interested in reporting a security vulnerability, refer to our [security policy](https://github.com/julelang/jule/security/policy).
 
-- Please read [Julenour Code of Conduct](https://jule.dev/code-of-conduct) before contributing anything
-- To contribute, please read the [contribution guidelines](https://jule.dev/contribute)
-- For discussions and asking questions, please use [discussions](https://github.com/julelang/jule/discussions)
-- Regarding security, please refer to the [security policy](https://github.com/julelang/jule/security/policy)
+Please read the [Julenour Code of Conduct](https://jule.dev/code-of-conduct) and the [contribution guidelines](https://jule.dev/contribute) before contributing.
 
 ## License