Skip to content

Commit e1584a2

Browse files
committed
fix readme
1 parent 307eb5c commit e1584a2

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

doc/content/_index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ First, you need to instantiate wrapper-manager's lib. This can be done by pullin
107107

108108
### Classic
109109

110-
Wrapper-manager can be pulled in a classic (non-flake) setup for a devshell or nixos configuration, like so:
110+
Wrapper-manager can be pulled in a classic (non-flake) setup for a dev-shell or NixOS configuration, like so:
111111

112112
```nix
113113
# shell.nix
@@ -139,7 +139,7 @@ in {
139139
Now that you already have `wrapper-manager` in scope, you need to evaluate `wrapper-manager.lib`. The argument is an attrset with following elements:
140140

141141
- `pkgs`: your nixpkgs instance used to bring `symlinkJoin` and `makeWrapper`, as well as passing it through the modules for convenience.
142-
- `modules`: a list of wrapper-manager modules. As with NixOS, a module can be passed as a path to a module or directly. A proper module is either an attset, or a function to attrset.
142+
- `modules`: a list of wrapper-manager modules. As with NixOS, a module can be passed as a path to a module or directly. A proper module is either an attrset, or a function to attrset.
143143
- `specialArgs` (optional): extra arguments passed to the module system.
144144

145145
A convenience shorthand for `(wrapper-manager.lib {...}).config.build.toplevel` is available through: `wrapper-manager.lib.build {}`, which is probably what you want in 99% of the cases.
@@ -164,7 +164,7 @@ A convenience shorthand for `(wrapper-manager.lib {...}).config.build.toplevel`
164164
# => «derivation /nix/store/...»
165165
```
166166

167-
For example, if you want to use wrapper-manager in the context of a devshell, you can instatiate it directly like so:
167+
For example, if you want to use wrapper-manager in the context of a dev-shell, you can instantiate it directly like so:
168168
```nix
169169
# pkgs and wrapper-manager in scope, see previous steps
170170
# ...
@@ -194,7 +194,7 @@ mkShell {
194194

195195
These are some examples of wrapper-manager used in the wild. Feel free to PR yours.
196196

197-
- https://github.com/viperML/dotfiles/tree/master/wrappers
197+
- https://github.com/viperML/dotfiles/tree/master/modules/wrapper-manager
198198

199199

200200
## To-do's

0 commit comments

Comments
 (0)