From f7a1e14451be9acfd176f4e14e8ab1529b8609da Mon Sep 17 00:00:00 2001 From: David Dworken Date: Sun, 9 Oct 2022 10:45:00 -0700 Subject: [PATCH] Fix typo --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 5a06d70..6984bed 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # hiSHtory: Better Shell History -`hishtory` is a better shell history. It stores your shell history in context (what directory you ran the command it, whether it succeeded or failed, how long it took, etc). This is all stored locally and end-to-end encrypted for syncing to to all your other computers. All of this is easily queryable via the `hishtory` CLI. This means from your laptop, you can easily find that complex bash pipeline you wrote on your server, and see the context in which you ran it. +`hishtory` is a better shell history. It stores your shell history in context (what directory you ran the command in, whether it succeeded or failed, how long it took, etc). This is all stored locally and end-to-end encrypted for syncing to to all your other computers. All of this is easily queryable via the `hishtory` CLI. This means from your laptop, you can easily find that complex bash pipeline you wrote on your server, and see the context in which you ran it. ![demo](https://raw.githubusercontent.com/ddworken/hishtory/master/backend/web/landing/www/img/hishtory.svg) @@ -84,4 +84,4 @@ When the user runs `hishtory query`, it retrieves all unread blobs from the back This all ensures that the minimalist backend cannot read your shell history, it only sees encrypted data. -If you find any security issues in hiSHtory, please reach out to `david@daviddworken.com`. \ No newline at end of file +If you find any security issues in hiSHtory, please reach out to `david@daviddworken.com`.