upstream/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-06-09 08:55:13 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 11

Update plugins.html.md (#2744)

Browse source 
Minor typo and spellcheck update
This commit is contained in:
Kenny Gatdula 2017-05-18 14:06:44 -04:00 committed by Vishal Nayak
parent fb15c97c6c
commit 77b728ca2c
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
website/source/docs/internals/plugins.html.md
View file

@ -64,7 +64,7 @@ When a backend wants to run a plugin, it first looks up the plugin, by name, in
the catalog. It then checks the executable's SHA256 sum against the one
configured in the plugin catalog. Finally vault runs the command configured in
the catalog, sending along the JWT formatted response wrapping token and mlock
settings (like Vault, plugins support the use of mlock when availible).
settings (like Vault, plugins support the use of mlock when available).
# Plugin Development
Because Vault communicates to plugins over a RPC interface, you can build and
@ -85,7 +85,7 @@ Developing a plugin is simple. The only knowledge necessary to write
a plugin is basic command-line skills and basic knowledge of the
[Go programming language](http://golang.org).
You're plugin implementation just needs to satisfy the interface for the plugin
Your plugin implementation needs to satisfy the interface for the plugin
type you want to build. You can find these definitions in the docs for the
backend running the plugin.