[DATALAD RUNCMD] run codespell throughout fixing typo automagically

=== Do not change lines below ===
{
 "chain": [],
 "cmd": "codespell -w",
 "exit": 0,
 "extra_inputs": [],
 "inputs": [],
 "outputs": [],
 "pwd": "."
}
^^^ Do not change lines above ^^^

README.md

@@ -94,7 +94,7 @@ The script will inform you once the installation is successful and add the ~/.pi
 
 ## Install from source
 
-`pixi` is 100% written in Rust and therefor it can be installed, build and tested with cargo.
+`pixi` is 100% written in Rust and therefore it can be installed, build and tested with cargo.
 To start using `pixi` from a source build run:
 
 ```shell
@@ -248,4 +248,4 @@ community. [Join our discord server today!][chat-url]
 <a name="pixibuilt"></a>
 ## Built using pixi
 
-To see whats being built with `pixi` check out the [Community](/docs/Community.md) page.
+To see what's being built with `pixi` check out the [Community](/docs/Community.md) page.

docs/advanced/advanced_tasks.mdx

@@ -130,7 +130,7 @@ Next to running actual executable like `./myprogram`, `cmake` or `python` the sh
 
 ### Syntax
 
-- **Boolean list:** use `&&` or `||` to seperate two commands.
+- **Boolean list:** use `&&` or `||` to separate two commands.
   - `&&`: if the command before `&&` succeeds continue with the next command.
   - `||`: if the command before `||` fails continue with the next command.
 - **Sequential lists:** use `;` to run two commands without checking if the fist command failed or succeeded.

docs/advanced/multi_platform_configuration.mdx

@@ -110,6 +110,6 @@ To deal with this you can define your activation scripts using the target defini
 scripts = ["setup.sh", "local_setup.bash"]
 
 [target.win-64.activation]
-scritps = ["setup.ps1", "setup.bat", "local_setup.bat"]
+scripts = ["setup.ps1", "setup.bat", "local_setup.bat"]
 ```
 When this project is run on `win-64` it will only execute the target scripts not the scripts specified in the default `activation.scripts`

docs/authentication.mdx

@@ -64,4 +64,4 @@ On Linux, one can use `GNOME Keyring` (or just Keyring) to access credentials th
 
 ## Fallback storage
 
-If you run on a server with none of the aformentioned keychains available, then pixi falls back to store the credentials in an _insecure_ JSON file. This JSON file is located at `~/.rattler/rattler_auth_store.json` and contains the credentials.
+If you run on a server with none of the aforementioned keychains available, then pixi falls back to store the credentials in an _insecure_ JSON file. This JSON file is located at `~/.rattler/rattler_auth_store.json` and contains the credentials.

docs/installation.mdx

@@ -44,7 +44,7 @@ The installer will download pixi and add it to the path.
 
 ### Install from source
 
-pixi is 100% written in Rust and therefor it can be installed, build and
+pixi is 100% written in Rust and therefore it can be installed, build and
 tested with cargo.
 To start using pixi from a source build run:
 

docs/vision.mdx

@@ -12,7 +12,7 @@ Modern package managers like `cargo` have shown us, how great a package manager
 We want to make pixi a great experience for everyone, so we have a few values that we want to uphold:
 
 1. **Fast**. We want to have a fast package manager, that is able to solve the environment in a few seconds.
-2. **User Friendly**. We want to have a package manager that puts user friendliness on the front-line. Providing easy, accesible and intuitive commands. That have the element of _least surprise_.
+2. **User Friendly**. We want to have a package manager that puts user friendliness on the front-line. Providing easy, accessible and intuitive commands. That have the element of _least surprise_.
 3. **Isolated Environment**. We want to have isolated environments, that are reproducible and easy to share. Ideally, it should run on all common platforms. The Conda packaging system provides an excellent base for this.
 4. **Single Tool**. We want to integrate most common uses when working on a development project with Pixi, so it should support at least dependency management, command management, building and uploading packages. You should not need to reach to another external tool for this.
 5. **Fun**. It should be fun to use pixi and not cause frustrations, you should not need to think about it a lot and it should generally just get out of your way.

examples/README.md

@@ -11,7 +11,7 @@ These are examples that are hosted in other repositories that use pixi for build
 
 ### AI
 
-[Lama.cpp](https://github.com/tdejager/llama.cpp)
+[Llama.cpp](https://github.com/tdejager/llama.cpp)
 
 ### Games
 

examples/opencv/README.md

@@ -1,5 +1,5 @@
 # OpenCV example
-OpenCV is a powerfull tool to do computer vision and fully opensource.
+OpenCV is a powerful tool to do computer vision and fully opensource.
 
 Here are some example on how to use it with `pixi`.
 
@@ -25,4 +25,4 @@ After that press `ESC` which will start the calibration.
 
 When the calibration is done the camera will be used again to find the distance to the checkerboard.
 
-![callibrated camera result](https://github.com/ruben-arts/pixi/assets/12893423/f42825d7-5010-4805-9f6b-b02075395413)
+![calibrated camera result](https://github.com/ruben-arts/pixi/assets/12893423/f42825d7-5010-4805-9f6b-b02075395413)

install/windows/main.wxs

@@ -206,7 +206,7 @@
 
                 1. Comment out or remove the two `Publish` tags that follow the
                    `WixVariable` tag.
-                2. Uncomment the `<WixVariable Id='WixUILicenseRtf' Value='Path\to\Eula.rft'>` tag futher down
+                2. Uncomment the `<WixVariable Id='WixUILicenseRtf' Value='Path\to\Eula.rft'>` tag further down
                 3. Replace the `Value` attribute of the `WixVariable` tag with
                    the path to a RTF file that will be used as the EULA and
                    displayed in the license agreement dialog.

src/cli/auth.rs

@@ -8,7 +8,7 @@ fn default_authentication_storage() -> AuthenticationStorage {
     AuthenticationStorage::new("rattler", &get_default_auth_store_location())
 }
 
-// moved into seperate function to access from info command
+// moved into separate function to access from info command
 pub fn get_default_auth_store_location() -> PathBuf {
     dirs::home_dir().unwrap().join(".rattler")
 }

src/cli/run.rs

@@ -141,7 +141,7 @@ pub async fn create_script(task: Task, args: Vec<String>) -> miette::Result<Sequ
     deno_task_shell::parser::parse(full_script.trim()).map_err(|e| miette!("{e}"))
 }
 
-/// Executes the given command withing the specified project and with the given environment.
+/// Executes the given command within the specified project and with the given environment.
 pub async fn execute_script(
     script: SequentialList,
     project: &Project,

src/environment.rs

@@ -397,7 +397,7 @@ pub async fn execute_transaction(
     // Open the package cache
     let package_cache = PackageCache::new(cache_dir.join("pkgs"));
 
-    // Create an install driver which helps limit the number of concurrent fileystem operations
+    // Create an install driver which helps limit the number of concurrent filesystem operations
     let install_driver = InstallDriver::default();
 
     // Define default installation options.

tests/install_tests.rs

@@ -90,7 +90,7 @@ async fn test_incremental_lock_file() {
         .unwrap();
 
     // Force using version 2 of `foo`. This should force `foo` to version `2` but `bar` should still
-    // remaing on `1` because it was previously locked
+    // remaining on `1` because it was previously locked
     pixi.add("foo >=2").await.unwrap();
 
     let lock = pixi.lock_file().await.unwrap();