style: use left-apos for words with u'll

docs/DEVELOPMENT.md

@@ -31,11 +31,11 @@ You can preview the production build with `npm run preview`.
 
 ## 🌳 Environment
 
-There are a few environment variables required for the app to function. You can find an overview under `.env.template`. You'll need access credentials for Pinata, Tenderly and a Gelato Relay API key for claiming projects. You'll also need to set up `PUBLIC_NETWORK`, as described right below.
+There are a few environment variables required for the app to function. You can find an overview under `.env.template`. Youʼll need access credentials for Pinata, Tenderly and a Gelato Relay API key for claiming projects. Youʼll also need to set up `PUBLIC_NETWORK`, as described right below.
 
 ## 🔗 Chain Config
 
-To run the app, you'll need to configure the `PUBLIC_NETWORK` environment variable. This should be the chainId of the chain you want to run the app for, and can currently be either 1, 5 or 11155111. The app will only allow connecting wallets that are set to this network, and all server-side requests will be made for this network's subgraph.
+To run the app, youʼll need to configure the `PUBLIC_NETWORK` environment variable. This should be the chainId of the chain you want to run the app for, and can currently be either 1, 5 or 11155111. The app will only allow connecting wallets that are set to this network, and all server-side requests will be made for this network's subgraph.
 
 For your convenience, weʼve deployed production mirrors of the app set to allow testnet connections:
 
@@ -68,7 +68,7 @@ To get started, make sure you have Docker installed & running, ensure the app's
 npm run e2e
 ```
 
-This will build a production version of the app, and execute all E2E test suites. Each test suite itself will run `docker compose up` to start the E2E test environment (ipfs node, anvil testnet w/ Drips contracts, and Graph Node w/ Drips subgraph). On first run, you'll see `Pinging Graph Node…` being logged for an extended amount of time. On subsequent runs, this step will be a lot faster, because much of the E2E Docker environment is being cached.
+This will build a production version of the app, and execute all E2E test suites. Each test suite itself will run `docker compose up` to start the E2E test environment (ipfs node, anvil testnet w/ Drips contracts, and Graph Node w/ Drips subgraph). On first run, youʼll see `Pinging Graph Node…` being logged for an extended amount of time. On subsequent runs, this step will be a lot faster, because much of the E2E Docker environment is being cached.
 
 **Important:** The local testnet is based on a static chain state which is copied into the testnet image from ./src/e2e-tests/docker/testnet/state. When a new version of contracts is released, this state needs to be updated. The subgraph is downloaded at image build time from the latest state of the `drips-subgraph` repo's `v2` branch.
 

src/lib/flows/edit-project-splits/steps/set-new-dependency-maintainer-split.svelte

@@ -28,7 +28,7 @@
 <StepLayout>
   <StepHeader
     headline="Split your funds"
-    description="Decide how much of your funds you’d like to split with your maintainers and dependencies from now on. You'll be able to edit your maintainer
+    description="Decide how much of your funds you’d like to split with your maintainers and dependencies from now on. Youʼll be able to edit your maintainer
     and dependency lists in the next step."
   />
   <VisualPercentageEditor

src/routes/app/(app)/projects/(forges)/components/become-supporter-card/become-supporter-card.svelte

@@ -111,7 +111,7 @@
     variant="primary">{dripList === null ? 'Create your Drip List' : 'Add to Drip List'}</Button
   >
   <div class="benefits typo-text-small">
-    {#if isSupportingProject}You're getting…{:else}You'll get…{/if}
+    {#if isSupportingProject}You're getting…{:else}Youʼll get…{/if}
     <div class="benefit">
       <Heart />
       <span>…to feel good about yourself, because you're helping fund open-source software.</span>