Update documentations. (#26)

Some updates to the documentation:

* Replace code-of-conduct with organization one.
* Cleanup `CONTRIBUTING.md`, `README.md` and `SECURITY.md` markdown.
* Remove `.txt` extension from `LICENSE` for consistency across repos.

Author: pjaton

CODE-OF-CONDUCT.md

@@ -6,24 +6,25 @@ Contributions to Containerization are welcomed and encouraged.
 
 We would love your contributions in the form of:
 
-* 🐛 Bug fixes
-* ⚡️ Performance improvements
-* ✨ API additions or enhancements
-* 📝 Documentation
-* 🧑‍💻 Project advocacy: blogs, conference talks, and more 
-* Anything else that could enhance the project!
+🐛 Bug fixes\
+⚡️ Performance improvements\
+✨ API additions or enhancements\
+📝 Documentation\
+🧑‍💻 Project advocacy: blogs, conference talks, and more
+
+Anything else that could enhance the project!
 
 ## Submitting Issues and Pull Requests
 
 ### Issues
 
 To file a bug or feature request, use [GitHub issues](https://github.com/apple/containerization/issues/new).
 
-🚧 For unexpected behavior or usability limitations, detailed instructions on how to reproduce the issue are appreciated. This will greatly help the priority setting and speed of which maintainers can get to your issue. 
+🚧 For unexpected behavior or usability limitations, detailed instructions on how to reproduce the issue are appreciated. This will greatly help the priority setting and speed of which maintainers can get to your issue.
 
 ### Pull Requests
 
-To make a pull request, use [GitHub](https://github.com/apple/containerization/compare). Please give the team a few days to review but it's ok to check in on occassion. We appreciate your contribution! 
+To make a pull request, use [GitHub](https://github.com/apple/containerization/compare). Please give the team a few days to review but it's ok to check in on occassion. We appreciate your contribution!
 
 > [!IMPORTANT]
 > If you plan to make substantial changes or add new features, we encourage you to first discuss them with the wider containerization developer community.
@@ -38,9 +39,9 @@ for the squashed commit. Think of it as the single, definitive description of yo
 
 Before merging, we'll review the pull request title and body to ensure it:
 
-*   Clearly and concisely describes the changes.
-*   Uses the imperative mood (e.g., "Add feature," "Fix bug").
-*   Provides enough context for future developers to understand the purpose of the change.
+* Clearly and concisely describes the changes.
+* Uses the imperative mood (e.g., "Add feature," "Fix bug").
+* Provides enough context for future developers to understand the purpose of the change.
 
 The pull request description should be concise and accurately describe the *what* and *why* of your changes.
 
@@ -49,17 +50,17 @@ The pull request description should be concise and accurately describe the *what
 Make sure your contributions are consistent with the rest of the project's formatting. You can do this using our Makefile:
 
 ```bash
-$ make fmt
+make fmt
 ```
 
 #### Applying License Header to New Files
 
 If you submit a contribution that adds a new file, please add the license header. You can do this using our Makefile:
 
 ```bash
-$ make update-licenses
+make update-licenses
 ```
 
 ## Code of Conduct
 
-To clarify of what is expected of our contributors and community members, the Containerization team has adopted the code of conduct defined by the Contributor Covenant. This document is used across many open source communities and articulates our values well. For more detail, please read the [Code of Conduct](/CODE-OF-CONDUCT.MD).
+To clarify of what is expected of our contributors and community members, the Containerization team has adopted the code of conduct defined by the Contributor Covenant. This document is used across many open source communities and articulates our values well. For more detail, please read the [Code of Conduct](https://github.com/apple/.github/blob/main/CODE_OF_CONDUCT.md "Code of Conduct").

CONTRIBUTING.md

@@ -4,6 +4,7 @@ The Containerization package allows applications to use Linux containers.
 Containerization is written in [Swift](https://www.swift.org) and uses [Virtualization.framework](https://developer.apple.com/documentation/virtualization) on Apple Silicon.
 
 Containerization provides APIs to:
+
 - Manage OCI images.
 - Interact with remote registries.
 - Create and populate ext4 file systems.
@@ -79,18 +80,21 @@ make cross-prep
 ```
 
 If you use a custom terminal application, you may need to move this command from `.zprofile` to `.zshrc` (replace `<USERNAME>`):
+
 ```bash
 # Added by swiftly
 . "/Users/<USERNAME>/.swiftly/env.sh"
 ```
 
 Restart the terminal application. Ensure this command returns `/Users/<USERNAME>/.swiftly/bin/swift` (replace `<USERNAME>`):
+
 ```bash
 which swift
 ```
 
 If you've installed or used a Static Linux SDK previously, you may need to remove older SDK versions from the system (replace `<SDK-ID>`):
-```
+
+```bash
 swift sdk list
 swift sdk remove <SDK-ID>
 ```
@@ -124,6 +128,6 @@ Preview the documentation by running in another terminal:
 open http://localhost:8000/documentation/
 ```
 
-## Contributing 
+## Contributing
 
 Contributions to Containerization are welcomed and encouraged. Please see [CONTRIBUTING.md](/CONTRIBUTING.md) for more information.

LICENSE.txt LICENSELICENSE.txt renamed to LICENSE

@@ -1,4 +1,4 @@
-# Security Disclosure Process 
+# Security disclosure process
 
 If you believe that you have discovered a security or privacy vulnerability in our open source software, please report it to us using the [GitHub private vulnerability feature](https://github.com/apple/containerization/security/advisories/new). Reports should include specific product and software version(s) that you believe are affected; a technical description of the behavior that you observed and the behavior that you expected; the steps required to reproduce the issue; and a proof of concept or exploit.