diff --git a/README.md b/README.md
index 413a7d8..e37d2f8 100644
--- a/README.md
+++ b/README.md
@@ -5,7 +5,7 @@ Take potentially dangerous PDFs, office documents, or images and convert them to
 ![Settings](./assets/screenshot1.png)
 ![Converting](./assets/screenshot2.png)
 
-Dangerzone works like this: You give it a document that you don't know if you can trust (for example, an email attachment). Inside of a sandbox, Dangerzone converts the document to a PDF (if it isn't already one), and then converts the PDF into raw pixel data: a huge list of of RGB color values for each page. Then, in a separate sandbox, Dangerzone takes this pixel data and converts it back into a PDF.
+Dangerzone works like this: You give it a document that you don't know if you can trust (for example, an email attachment). Inside of a sandbox, Dangerzone converts the document to a PDF (if it isn't already one), and then converts the PDF into raw pixel data: a huge list of RGB color values for each page. Then, in a separate sandbox, Dangerzone takes this pixel data and converts it back into a PDF.
 
 _Read more about Dangerzone in the blog post [Dangerzone: Working With Suspicious Documents Without Getting Hacked](https://tech.firstlook.media/dangerzone-working-with-suspicious-documents-without-getting-hacked)._
 
@@ -40,4 +40,4 @@ Dangerzone can convert these types of document into safe PDFs:
 
 Dangerzone was inspired by [Qubes trusted PDF](https://blog.invisiblethings.org/2013/02/21/converting-untrusted-pdfs-into-trusted.html), but it works in non-Qubes operating systems. It uses containers as sandboxes instead of virtual machines (using Docker for macOS, Windows, and Debian/Ubuntu, and [podman](https://podman.io/) for Fedora).
 
-Set up a development environment by following [these instructions](/BUILD.md).
\ No newline at end of file
+Set up a development environment by following [these instructions](/BUILD.md).