kjuulh/dagger
Archived
1
0
Fork 0
Code Issues 1 Pull Requests 1 Projects Releases Wiki Activity

Merge pull request #577 from aluzzardi/docs-superglu-typo

Browse Source 
docs: fix "superglu" typo
This commit is contained in:
Andrea Luzzardi 2021-06-07 11:28:12 -07:00 committed by GitHub
commit e3ee7f2568
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -10,7 +10,7 @@ to any infrastructure, in just a few lines of code.
The Dagger platform adapts to your application, not the other way around. The Dagger platform adapts to your application, not the other way around.
Thanks to its ecosystem of reusable packages and flexible scripting system, Thanks to its ecosystem of reusable packages and flexible scripting system,
Dagger can be dropped into any software project without requiring changes to Dagger can be dropped into any software project without requiring changes to
its architecture or workflow. Think of it as your "devops superglu". its architecture or workflow. Think of it as your "devops superglue".
No matter how your deployment works under the hood, you can manage it with the No matter how your deployment works under the hood, you can manage it with the
same Dagger user interface. This makes developers more productive, because they same Dagger user interface. This makes developers more productive, because they

2
docs/README.md
View File

@ -16,7 +16,7 @@ in just a few lines of code.
The Dagger platform adapts to your application, not the other way around. The Dagger platform adapts to your application, not the other way around.
Thanks to its ecosystem of reusable packages and flexible scripting system, Dagger can be dropped Thanks to its ecosystem of reusable packages and flexible scripting system, Dagger can be dropped
into any software project without requiring changes to its architecture or workflow. into any software project without requiring changes to its architecture or workflow.
Think of it as your "devops superglu". Think of it as your "devops superglue".
No matter how your deployment works under the hood, you can manage it with the same Dagger user interface. No matter how your deployment works under the hood, you can manage it with the same Dagger user interface.
This makes developers more productive, because they don't have to learn a new workflow every time their deployment This makes developers more productive, because they don't have to learn a new workflow every time their deployment

2
tests/README.md
View File

@ -2,7 +2,7 @@
## TL;DR ## TL;DR
``` ```shell
# Install dependancies # Install dependancies
yarn install yarn install