From b928993510b9c4633ffcf74de401b5c7453ff137 Mon Sep 17 00:00:00 2001
From: Doug Andrade <contact@dougandrade.com>
Date: Sun, 28 May 2023 20:06:43 -0400
Subject: [PATCH] typo: /ressources >> /resources

---
 README.md                                          |  10 ++++------
 apps/web/{ressources => resources}/certificate.p12 | Bin
 apps/web/{ressources => resources}/example.pdf     | Bin
 packages/signing/addDigitalSignature.ts            |   2 +-
 4 files changed, 5 insertions(+), 7 deletions(-)
 rename apps/web/{ressources => resources}/certificate.p12 (100%)
 rename apps/web/{ressources => resources}/example.pdf (100%)

diff --git a/README.md b/README.md
index 26316054f..0861312fb 100644
--- a/README.md
+++ b/README.md
@@ -78,8 +78,6 @@ The current project goal is to <b>[release a production ready version](https://g
 
 - To contribute please see our [contribution guide](https://github.com/documenso/documenso/blob/main/CONTRIBUTING.md).
 
-
-
 # Tech
 
 Documenso is built using awesome open source tech including:
@@ -123,7 +121,7 @@ Want to get up and running quickly? Follow these steps:
   - This will spin up a postgres database and inbucket mail server in docker containers.
 - Run `npm run dev` in the root directory
 - Want it even faster? Just use
-    ```sh
+  ```sh
   npm run d
   ```
 
@@ -157,10 +155,10 @@ Follow these steps to setup documenso on you local machine:
 ---
 
 - Optional: Seed the database using <code>npm run db-seed</code> to create a test user and document
-- Optional: Upload and sign <code>apps/web/ressources/example.pdf</code> manually to test your setup
+- Optional: Upload and sign <code>apps/web/resources/example.pdf</code> manually to test your setup
 
 - Optional: Create your own signing certificate
-  - A demo certificate is provided in `/app/web/ressources/certificate.p12`
+  - A demo certificate is provided in `/app/web/resources/certificate.p12`
   - To generate your own using these steps and a Linux Terminal or Windows Subsystem for Linux (WSL) see **[Create your own signing certificate](#creating-your-own-signing-certificate)**.
 
 ## Updating
@@ -185,7 +183,7 @@ For the digital signature of your documents you need a signing certificate in .p
 3. Combine the private key and the self-signed certificate to create the p12 certificate. You can run the following command to do this: \
    <code>openssl pkcs12 -export -out certificate.p12 -inkey private.key -in certificate.crt</code>
 4. You will be prompted to enter a password for the p12 file. Choose a strong password and remember it, as you will need it to use the certificate (**can be empty for dev certificates**)
-5. Place the certificate <code>/apps/web/ressource/certificate.p12</code>
+5. Place the certificate <code>/apps/web/resources/certificate.p12</code>
 
 # Docker
 
diff --git a/apps/web/ressources/certificate.p12 b/apps/web/resources/certificate.p12
similarity index 100%
rename from apps/web/ressources/certificate.p12
rename to apps/web/resources/certificate.p12
diff --git a/apps/web/ressources/example.pdf b/apps/web/resources/example.pdf
similarity index 100%
rename from apps/web/ressources/example.pdf
rename to apps/web/resources/example.pdf
diff --git a/packages/signing/addDigitalSignature.ts b/packages/signing/addDigitalSignature.ts
index f4f565c8f..8bd219bb5 100644
--- a/packages/signing/addDigitalSignature.ts
+++ b/packages/signing/addDigitalSignature.ts
@@ -10,7 +10,7 @@ export const addDigitalSignature = async (documentAsBase64: string): Promise<str
   const pdfBuffer = Buffer.from(documentAsBase64, "base64");
   const p12Buffer = Buffer.from(
     fs
-      .readFileSync(process.env.CERT_FILE_PATH || "ressources/certificate.p12")
+      .readFileSync(process.env.CERT_FILE_PATH || "resources/certificate.p12")
       .toString(process.env.CERT_FILE_ENCODING ? undefined : "binary"),
     (process.env.CERT_FILE_ENCODING as BufferEncoding) || "binary"
   );