chore: 🔧 Standardize contractions

Standardized contractions in various markdown files for consistency and readability. Replaced instances of "it’s" with "it's", "doesn’t" with "doesn't", and similar contractions across all documents.

Blockchain.md

@@ -1,7 +1,7 @@
 # Blockchain
 
 - [A blockchain is a decentralized [[Databases|database]]](https://www.youtube.com/watch?v=bBC-nXj3Ng4).
-  - A blockchain is a worse database. It is slower, requires way more storage and compute, doesn’t have customer support, etc. [But has one dimension along which it is radically different. No single entity or small group of entities controls it](https://continuations.com/post/671863718643105792/web3crypto-why-bother).
+  - A blockchain is a worse database. It is slower, requires way more storage and compute, doesn't have customer support, etc. [But has one dimension along which it is radically different. No single entity or small group of entities controls it](https://continuations.com/post/671863718643105792/web3crypto-why-bother).
 - Blockchain solve the Byzantine Generals Problem: [How do participants in a decentralized network communicate and coordinate with each other towards some action without relying on a trusted third-party?](https://a16z.com/2019/11/08/crypto-glossary/).
   - Blockchains are "trustless". There are mechanisms in place by which all parties in the [[Systems|system]] can reach a consensus on what the canonical truth is.
   - Power and trust is distributed (or shared) among the network's stakeholders (e.g. developers, miners, and consumers), rather than concentrated in a single individual or entity (e.g. banks, governments, and financial institutions).

Blogging.md

@@ -32,4 +32,4 @@
   2. A few references. Connect the dots between some links, quotes from other sources.
   3. An anecdote from your own work that provides rich texture and context for what you do.
   4. Some open questions that invite people to discuss.
-- [Keep making your post more opinionated until it reflects your true beliefs](https://twitter.com/HamelHusain/status/1751995737095709164). Don’t hedge. People want to hear what you think!
+- [Keep making your post more opinionated until it reflects your true beliefs](https://twitter.com/HamelHusain/status/1751995737095709164). Don't hedge. People want to hear what you think!

Company Knowledge Management.md

@@ -11,7 +11,7 @@ If we think about a company as an organism, then a **knowledge management system
 There are some basic principles and [[values]] that will make maintaining and evolving a knowledge base easier over time.
 
 - **Transparency**. Everyone has access to everything.
-- **Iterative Improvements**. Everything is a WIP. No need to say it’ll be updated later or add dates to pages.
+- **Iterative Improvements**. Everything is a WIP. No need to say it'll be updated later or add dates to pages.
 - **Permissionless**. Anyone is able to edit anything. Similar to GitHub Pull Requests. Later, the resource owner can accept or reject the change.
 - **Interconnected**. Links between everything!
 
@@ -36,7 +36,7 @@ There are some basic principles and [[values]] that will make maintaining and ev
 - [Decisions (and rationale) must be documented in a durable location. At GitHub they used to say everything should have a URL](https://haacked.com/archive/2020/04/07/introducing-aboard-beta/). That gives the company a **Decision Log**.
 - Important documents like Roadmaps should be easy to discover and people should be able to comment on and have discussions around them. That promotes keeping it up to date.
 - [[Design Docs]] should have an explicit place, also acting as an historical log.
-- [[Documentation]] should have a common entry point to increase discovery. Each team can have it’s own [[processes]] on top.
+- [[Documentation]] should have a common entry point to increase discovery. Each team can have it's own [[processes]] on top.
 - At a company level, each team documents differently. To make the most of that, grow the knowledge organically and locally, not top down. Each team should have its own permissionless and open way of working and should be made public to the rest of the company. That way they can evolve the system to fit their needs. Then, there is a standard protocol to share information between teams.
   - The protocol serves as the team communications API. An abstraction over the inner works of the team that is common to all the other teams.
   - E.g: Each team having a homepage README with links to their slack, ticket system and processes.
@@ -60,7 +60,7 @@ Whenever you need to thoroughly brief a group of people on an important matter,
 2. Objective. **What** you want to achieve.
 3. Plan. **How** you want to achieve it.
 4. Logistics. What budget and resources are available, and how they are used.
-5. Communications. How you’ll be coordinating among yourselves and with others in order to achieve your goal.
+5. Communications. How you'll be coordinating among yourselves and with others in order to achieve your goal.
 
 ## Resources
 

Curiosity.md

@@ -5,7 +5,7 @@
 - Never stop [[learning]], practice [[Thinking|rational thinking]] and internalize [[mental models]] and other concepts that will help you think more effectively.
 - Knowledge is a powerful tool. The more you [feel like a noob](http://paulgraham.com/noob.html), the better. Feeling stupid now is better than feeling stupid in 10 years.
 - [Reality has a surprising amount of detail](http://johnsalvatier.org/blog/2017/reality-has-a-surprising-amount-of-detail). Knowing more about the world makes you enjoy it more. [Understanding how music is made increases the pleasure you get from music](https://youtu.be/JbVfcZxfIZo).
-  - Real things exist in essentially infinite resolution. [Looking closer always reveals more, and it’s often not what you’d expect](https://www.raptitude.com/2023/10/the-truth-is-always-made-of-details/).
+  - Real things exist in essentially infinite resolution. [Looking closer always reveals more, and it's often not what you'd expect](https://www.raptitude.com/2023/10/the-truth-is-always-made-of-details/).
 - Do stuff! Whatever is you work on, is worthwhile as long as you share your learnings. In the worst case, if your [[ideas]] don't work out, the community will learn why that approach doesn't make sense.
   - Remix ideas. Ideas are impacted by [[evolution]]. The most useful ones survive and evolve. [Innovation is product of the combinations of ideas](https://youtu.be/XUAIIQFoufs). Everything is a remix!
   - Fail early and often. There is only one guaranteed way you'll won't get something you want, and that's not to pursue it. [Mistakes](https://meta.wikimedia.org/wiki/So_you%27ve_made_a_mistake_and_it%27s_public...) are the portals of discovery.

Data/Dashboards.md

@@ -70,6 +70,6 @@ The value is that now discussions are happening about the data.
   - That the data is correct.
   - That the transformation logic is correct.
   - That the data is complete.
-- The dashboard is always just a snapshot of "what" is happening, but knowing the underlying base level data is always needed to understand "why" it’s happening.
+- The dashboard is always just a snapshot of "what" is happening, but knowing the underlying base level data is always needed to understand "why" it's happening.
 - Usually, answers don't lead to Eureka moments, they lead to follow up questions and follow up questions.
 - Having 20 dashboards means one is always likely to be up or down by a statistically significant amount.

Data/Data Practices.md

@@ -80,8 +80,8 @@ The aim is to answer the following questions each time:
 2. **What should I learn from this?** or, Why should I care? Include the **most useful information,** and/or a **clear takeaway**. For folks who only have a few seconds to scan the message, it should be **easy to spot** the **most valuable** bit of the insight, the **reason** this exploration was considered worth sharing.
 3. **What caught my eye?** Share a chart or a related resource!
 4. **What if I want to know more?** A **link to additional information** can be valuable for people who have time for more than a quick scan and want to understand how you developed the insight, or do some of their own related exploration.
-5. **What if I have a question?** Explicitly **inviting questions** and responses is crucial. It’s the best part of sharing an insight! This is where you get to learn about things your colleagues know that you don’t, or what they’re curious about but has not yet risen to the level of becoming a data request from them.
-6. **What if posting this prompts a whole bunch of follow-up questions, or exposes incorrect assumptions?** If you have hit on something that’s interesting to a lot of people there likely will be questions that spin off, new ways to slice the data you’re looking at, or assumptions you have made that need to be corrected.
+5. **What if I have a question?** Explicitly **inviting questions** and responses is crucial. It's the best part of sharing an insight! This is where you get to learn about things your colleagues know that you don't, or what they're curious about but has not yet risen to the level of becoming a data request from them.
+6. **What if posting this prompts a whole bunch of follow-up questions, or exposes incorrect assumptions?** If you have hit on something that's interesting to a lot of people there likely will be questions that spin off, new ways to slice the data you're looking at, or assumptions you have made that need to be corrected.
 
 ### Slack Template
 

Data/Data Quality.md

@@ -12,7 +12,7 @@
 - [[Data Culture|Data is a product]] and that means that you can do postmortems (5 whys) and incident reports on data quality issues.
 - [There are two strategies to detect quality issues](https://towardsdatascience.com/data-observability-vs-data-testing-everything-you-need-to-know-6f3d7193b388):
   - Data Testing. Involves checking `null` values, distributions, uniqueness, known invariants, etc.
-  - Data Observability. Since you can’t predict all the failure modes, you can use automated monitoring, alerting, and triaging to identify and evaluate data quality issues.
+  - Data Observability. Since you can't predict all the failure modes, you can use automated monitoring, alerting, and triaging to identify and evaluate data quality issues.
 - Four categories of characteristics about your data form [the four pillars of Data Observability](https://www.metaplane.dev/blog/the-four-pillars-of-data-observability):
   1. The *Metrics* and *Metadata* pillars describe the internal characteristics of our data itself and its external characteristics
   2. The *Lineage* and *Logs* pillars describe internal dependencies within our data and its interactions with the external world data at any point in time.

Data/Experimentation.md

@@ -19,14 +19,14 @@ We do not live in an ideal world, so we need to be very deliberate and thoughtfu
 - Generate hypotheses based on actual observations. All experiments should have a hypothesis in plain English.
 - Do not simply copy what other companies are doing (do not assume that other companies tested and validated something).
 - Choose one primary metric in advance to determine "winner" while keeping a few guardrail metrics.
-- [You're probably **not measuring what you thought you were measuring**](https://www.lesswrong.com/posts/9kNxhKWvixtKW5anS/you-are-not-measuring-what-you-think-you-are-measuring). But if you measure enough different stuff, you might figure out what you’re actually measuring.
+- [You're probably **not measuring what you thought you were measuring**](https://www.lesswrong.com/posts/9kNxhKWvixtKW5anS/you-are-not-measuring-what-you-think-you-are-measuring). But if you measure enough different stuff, you might figure out what you're actually measuring.
   - Log generously.
 - Stack rank all ideas based on level of effort and potential impact -- also required sample size/run time to get results.
 - Continuously validate tracking implementation.
 - Think carefully when choosing your randomization unit.
 - Run more A/A tests.
 - The best two places to run an A/B test: In early planning(what kinds of story do people want) and when adding finishing touches(alternative versions of a scene).
-- Remember, you’re measuring averages.
+- Remember, you're measuring averages.
 - A great way to help people understand the importance of healthy scrutiny and [how our biases work](https://www.goodreads.com/book/show/11468377-thinking-fast-and-slow) can be to do a session where people guess the impact of an A/B test before you reveal it.
 
 You can use [online calculators](http://experimentcalculator.com/) to estimate the length of an experiment. If your experiment is estimated to take a very long time, you can go for a different metric with a higher baseline rate or only care about bigger changes.
@@ -36,7 +36,7 @@ You can use [online calculators](http://experimentcalculator.com/) to estimate t
 - Experiment summary:
   - We believe that... {describe your hypothesis in one sentence}.
   - To verify that, we will... {describe your test in one sentence}.
-  - And we’ll measure the impact on... {metrics}.
+  - And we'll measure the impact on... {metrics}.
 - Hypothesis. What are we expecting to happen? What can we monitor to detect problems with this?
 - Business problem
 - Supporting data

Data/Machine Learning.md

@@ -17,7 +17,7 @@ These points are expanded with more details in courses like [Made With ML](https
 ## Tips
 
 - Use pre-commit hooks. Start with the basics — black, isort — then add pydocstyle, mypy, check-ast, ...
-- Version your data! Don’t overwrite raw datasets.
+- Version your data! Don't overwrite raw datasets.
 
 ### ML In Production Resources
 

Data/Metrics.md

@@ -25,7 +25,7 @@
 - [Every metric you use should have an Operational Definition](https://twitter.com/ejames_c/status/1732621626259484953).
   1. A criterion — the thing you want to measure.
   2. Test procedure — how will you measure the thing?
-  3. Decision rule — how will you decide if the thing you’re measuring should be included in the count?
+  3. Decision rule — how will you decide if the thing you're measuring should be included in the count?
 - A process is predictable if it just contains routine variation. It is unpredictable if it contains both routine and special variation. You can only improve a process if you first make it predictable.
 - Metrics should help forming a working causal model of the business you're in so you know what interventions you can make and can predict the consequences.
 

Data/Product Analytics.md

@@ -9,7 +9,7 @@ Product analytics can be defined as the way companies analyze what their users a
 - [Have one clear owner for: event implementation, QA, stakeholder buy-in on metrics from events. For each of these areas, ownership extends forever to make sure there are no regressions](https://twitter.com/sarahmk125/status/1521814508045582336).
 - Measure tracking quality and treat all tracking bugs as production incidents.
 - Data trust issues come when data producers and data consumers doesn't work together. Aim to shorten the data loop. E.g: [The feedback loop for the performance engineer is much faster and reliable (same person tracks and analyzes) than for the standard engineer that doesn't look at the data to see the impact they made with their changes](https://www.heavybit.com/library/podcasts/the-right-track/ep-8-defining-the-data-scientist-with-josh-wills-of-weavegrid/).
-- [Product Analytics is hard because when you instrument the events you don’t know what you want to analyze. When you analyze them you often didn’t capture what you want to measure](https://twitter.com/pedram_navid/status/1511362347490631782). Also, Ad-Blockers.
+- [Product Analytics is hard because when you instrument the events you don't know what you want to analyze. When you analyze them you often didn't capture what you want to measure](https://twitter.com/pedram_navid/status/1511362347490631782). Also, Ad-Blockers.
 - Even tracking is seen as an after-the-fact activity instead of something integrated into day-to-day design and development.
   - No one gets promoted for doing a good tracking work. People get promoted for delivering features.
 - [Some of hard things](https://twitter.com/_MRogers/status/1511426752735760392): building a common nomenclature, knowing what exists, what's reusable/equivalent in new features, testing, aligning across different platforms...

Decentralized Autonomous Organizations.md

@@ -5,7 +5,7 @@
 
 ## Resources
 
-- [A beginner’s guide to DAOs](https://linda.mirror.xyz/Vh8K4leCGEO06_qSGx-vS5lvgUqhqkCz9ut81WwCP2o).
+- [A beginner's guide to DAOs](https://linda.mirror.xyz/Vh8K4leCGEO06_qSGx-vS5lvgUqhqkCz9ut81WwCP2o).
 - [Everything you need to know about DAOs](https://foundation.app/blog/everything-you-need-to-know-about-daos).
 - [The Handbook of Handbooks for Decentralized Organizing](https://hackmd.io/@yHk1snI9T9SNpiFu2o17oA/Skh_dXNbE?type=view).
 - [Resources For Decentralized Organizing](https://commonslibrary.org/resources-for-decentralised-organising/). Also [summarized in slides](https://geo.coop/sites/default/files/patterns_of_decentralized_organizing.pdf).

Decentralized Protocols.md

@@ -21,7 +21,7 @@
 - **[Progressive decentralization](https://a16zcrypto.com/content/article/progressive-decentralization-crypto-product-management/) optional centralization.**
   - A decentralized protocol can work with a centralized provider. It has the benefits of both (might be fast but no lock users in).
 - A major downside of decentralized protocols/networks is that they tend to perform poorly. Hubs are efficient.
-- [It's the properties decentralization gives us that we care about, not decentralization itself](https://haseebq.com/why-decentralization-isnt-as-important-as-you-think/). Decentralization is a global, emergent property. You can feel latency, you can feel transaction fees, but networks ostensibly feel the same whether they’re centralized or decentralized. Decentralization is valuable when it lets you do new things fundamentally better, not old things fundamentally worse.
+- [It's the properties decentralization gives us that we care about, not decentralization itself](https://haseebq.com/why-decentralization-isnt-as-important-as-you-think/). Decentralization is a global, emergent property. You can feel latency, you can feel transaction fees, but networks ostensibly feel the same whether they're centralized or decentralized. Decentralization is valuable when it lets you do new things fundamentally better, not old things fundamentally worse.
 - Ultimately, [users don't care about decentralization](https://news.ycombinator.com/item?id=38694551). Most of the time, it doesn't matter if the service is distributed or comes from a single server sitting in someone's basement. Users want to use services (chat, write mails, watch videos, have a website, buy stuff, sell stuff) and not run infrastructure of any kind. Decentralization is a means to an end, not an end in itself.
 - If a system requires a centralized part, a great alternative is give the user the ability to point to other centralized things taking care of that part.
 - If you have a protocol, try enforcing the desired behavior using the protocol. Your ideas of how to solve it might not be the best and adding a protocol restriction (incentives/penalties) will make people figure out.

Documentation.md

@@ -10,7 +10,7 @@
   - A how-to guide is goal-oriented, shows how to solve a specific problem with a series of steps. E.g: a recipe in a cookery book.
   - An explanation is understanding-oriented, provides background and context. E.g: an article on culinary social history.
   - A reference guide is information-oriented, describes the machinery and is accurate and complete. E.g: a reference encyclopedia article.
-- [If someone’s having to read your docs, it’s not "simple"](https://justsimply.dev/). Remove filler words.
+- [If someone's having to read your docs, it's not "simple"](https://justsimply.dev/). Remove filler words.
 - [Principles to keep in mind when writing documentation](https://mkaz.blog/misc/notes-on-technical-writing/).
   - The purpose of technical writing is to help users accomplish tasks as quickly and effectively as possible.
   - People learn by doing, prefer to be shown and not told.

Dogs.md

@@ -110,4 +110,4 @@
 
 - [Dog Training Reddit Wiki](https://www.reddit.com/r/Dogtraining/wiki/index)
 - [Kikopup Youtube Channel](https://www.youtube.com/user/kikopup)
-- [Zak George’s Youtube Channel](https://www.youtube.com/channel/UCZzFRKsgVMhGTxffpzgTJlQ)
+- [Zak George's Youtube Channel](https://www.youtube.com/channel/UCZzFRKsgVMhGTxffpzgTJlQ)