Skip to content

Commit 91eda15

Browse files
yarikopticmartin-schulze-vireso
authored andcommitted
[DATALAD RUNCMD] run codespell throughout
=== Do not change lines below === { "chain": [], "cmd": "codespell -w", "exit": 0, "extra_inputs": [], "inputs": [], "outputs": [], "pwd": "." } ^^^ Do not change lines above ^^^
1 parent ac8491b commit 91eda15

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -856,7 +856,7 @@ error message on the standard error.
856856

857857
```
858858
-- ERROR: temp_make --
859-
mktemp: failed to create directory via template ‘/etc/samle.bats-1-XXXXXXXXXX’: Permission denied
859+
mktemp: failed to create directory via template ‘/etc/sample.bats-1-XXXXXXXXXX’: Permission denied
860860
--
861861
```
862862

@@ -897,7 +897,7 @@ error message on the standard error.
897897

898898
```
899899
-- ERROR: temp_del --
900-
rm: cannot remove '/etc/samle.bats-1-04RUVmBP7x': No such file or directory
900+
rm: cannot remove '/etc/sample.bats-1-04RUVmBP7x': No such file or directory
901901
--
902902
```
903903

@@ -980,7 +980,7 @@ path : <temp>/path/to/non-existent-file
980980

981981
## **Development**
982982

983-
No one would want to develop piece of bash dependant libraries on their laptops due to single mistake (globbing for instance) can cause a disaster. In order to prevent this there is a Vagrantfile that you can use.
983+
No one would want to develop piece of bash dependent libraries on their laptops due to single mistake (globbing for instance) can cause a disaster. In order to prevent this there is a Vagrantfile that you can use.
984984

985985
In order to start development environment, you have to take two steps;
986986

@@ -990,7 +990,7 @@ user@localhost:~/bats-file$ vagrant up
990990

991991
The line above spins up a brand new virtualbox image and provisions with prerequisites.
992992

993-
However, as the tests require not to be on a network share due to running commands eg: `mknod`, the files are shared into the VM by `rsync` module. Rsync in vagrant only runs initialy and stops. During the active development, you regularly change files and might want to see the impact. To achieve that, you have to use auto rsync.
993+
However, as the tests require not to be on a network share due to running commands eg: `mknod`, the files are shared into the VM by `rsync` module. Rsync in vagrant only runs initially and stops. During the active development, you regularly change files and might want to see the impact. To achieve that, you have to use auto rsync.
994994

995995
> `auto-rsync` is a long running command. It means that it has to run on terminal screen as long as the VM is up and running. So, you have to keep this in a dedicated terminal screen.
996996

0 commit comments

Comments
 (0)