From d6fd631dca671ee774794aa1bb513744b56a7093 Mon Sep 17 00:00:00 2001 From: Anna Powell-Smith Date: Wed, 7 Aug 2024 19:41:31 +0100 Subject: [PATCH] =?UTF-8?q?Fix=20typos=20=F0=9F=94=8E=20(#9127)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Fix typos. A few typos in the handbook, startup signup form and docs. --------- Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com> --- contents/handbook/engineering/incidents.md | 2 +- .../engineering/posthog-com/developing-the-website.md | 2 +- contents/handbook/growth/marketing/components.mdx | 2 +- contents/handbook/growth/marketing/writing-for-posthog.md | 2 +- contents/handbook/growth/sales/billing.md | 2 +- contents/handbook/growth/sales/new-sales.md | 4 ++-- contents/handbook/growth/sales/sales-operations.md | 2 +- contents/handbook/people/hiring-process/index.md | 6 +++--- .../handbook/product/enterprise-features-prioritization.md | 2 +- contents/handbook/product/per-product-growth-reviews.md | 6 +++--- contents/handbook/product/product-team.md | 4 ++-- contents/tutorials/android-session-replay.md | 2 +- contents/tutorials/anthropic-analytics.md | 2 +- src/components/People/index.tsx | 2 +- .../Pricing/PricingCalculator/Tabs/ProductAnalytics.tsx | 2 +- src/components/Pricing/PricingExperiment.tsx | 2 +- src/components/Product/FeatureFlags/index.tsx | 2 +- src/components/Startups/index.tsx | 4 ++-- src/pages/docs/product-analytics.tsx | 2 +- src/pages/privacy.tsx | 2 +- src/templates/merch/Product.tsx | 2 +- src/templates/merch/ProductPanel.tsx | 2 +- 22 files changed, 29 insertions(+), 29 deletions(-) diff --git a/contents/handbook/engineering/incidents.md b/contents/handbook/engineering/incidents.md index 2f130de8df4f..0fb2658b66df 100644 --- a/contents/handbook/engineering/incidents.md +++ b/contents/handbook/engineering/incidents.md @@ -89,7 +89,7 @@ When updating the status page, make sure to mark the affected component appropri status -Occasionally it may be desirable to do addditional customer communications, such as sending an email to impacted customers or making updates to [the service page](/service-message). Comms will organize and write these communications for you, so please let them know if this is needed. Joe is usually the best initial point of contact. +Occasionally it may be desirable to do additional customer communications, such as sending an email to impacted customers or making updates to [the service page](/service-message). Comms will organize and write these communications for you, so please let them know if this is needed. Joe is usually the best initial point of contact. ## When does an incident end? diff --git a/contents/handbook/engineering/posthog-com/developing-the-website.md b/contents/handbook/engineering/posthog-com/developing-the-website.md index d423ea5997e7..6472adb25766 100644 --- a/contents/handbook/engineering/posthog-com/developing-the-website.md +++ b/contents/handbook/engineering/posthog-com/developing-the-website.md @@ -257,7 +257,7 @@ import { ComparisonHeader } from 'components/ComparisonTable/header' ``` - + ``` diff --git a/contents/handbook/growth/marketing/components.mdx b/contents/handbook/growth/marketing/components.mdx index 453f3348cd89..421d2b6aad8e 100644 --- a/contents/handbook/growth/marketing/components.mdx +++ b/contents/handbook/growth/marketing/components.mdx @@ -33,7 +33,7 @@ Then, customize the code below to fit your needs. ```jsx - + ``` diff --git a/contents/handbook/growth/marketing/writing-for-posthog.md b/contents/handbook/growth/marketing/writing-for-posthog.md index baedf2f9ea54..a77481e90000 100644 --- a/contents/handbook/growth/marketing/writing-for-posthog.md +++ b/contents/handbook/growth/marketing/writing-for-posthog.md @@ -100,7 +100,7 @@ The main folders are: - `/contents/founders` – Articles for the [Founder content hub](/founders). - `/contents/product-engineers` – Articles for the [Product engineer content hub](/product-engineers) - `/contents/tutorials` – Tutorials -- `/content/cusomters` – Customer stories +- `/content/customers` – Customer stories - `/contents/spotlight` – Startup spotlight **Important:** Some articles can rightfully belong in both the founder hub _and_ the product engineers hub. In this case, choose the most appropriate hub folder and then add the `crosspost:` field to your frontmatter so it appears in both. So, add `crosspost: product-engineers` to post a founder's hub article in product engineers as well, and vice versa. You can also add tags from either hub like normal. diff --git a/contents/handbook/growth/sales/billing.md b/contents/handbook/growth/sales/billing.md index 680c0f8b8bae..debc4fb7e9fa 100644 --- a/contents/handbook/growth/sales/billing.md +++ b/contents/handbook/growth/sales/billing.md @@ -43,7 +43,7 @@ If this is a new contract for an existing customer, you will need to add their e ###### Step 4: Apply credits - Make sure that the payment is fully processed to avoid any automatic deductions. -- **If customer wishes to begin using credits immediately:** return to the Zapier table after you’ve verified payment competion and click the "Apply Credit" button. +- **If customer wishes to begin using credits immediately:** return to the Zapier table after you’ve verified payment completion and click the "Apply Credit" button. - **If customer wishes to begin using credits in the next billing cycle:** ask the RevOps team to apply the credits at the end of the current billing cycle. ###### Step 5: Schedule subscription diff --git a/contents/handbook/growth/sales/new-sales.md b/contents/handbook/growth/sales/new-sales.md index 29100203a4ad..ffb75b34c2d7 100644 --- a/contents/handbook/growth/sales/new-sales.md +++ b/contents/handbook/growth/sales/new-sales.md @@ -117,7 +117,7 @@ Set yourself a reminder for halfway through their evaluation period to look at t Most customers don't need this beyond sharing our existing documentation. This step often occurs in parallel with product evaluation. Usually only bigger companies ask for this. -If the customer requires a vendor questionnaire or security questionnaire then it's best for the AE involved to try and fill it out. If a company reaches out initially with this request, it's often best to try and understand if the customer has an intenton to pay or at least grow into a paying customer before investing a lot of time filling it out. If there are any questions that are unclear post the specific question in #team-people-and-ops channel. +If the customer requires a vendor questionnaire or security questionnaire then it's best for the AE involved to try and fill it out. If a company reaches out initially with this request, it's often best to try and understand if the customer has an intention to pay or at least grow into a paying customer before investing a lot of time filling it out. If there are any questions that are unclear post the specific question in #team-people-and-ops channel. If you need help with anything data privacy or [MSA-related](/handbook/growth/sales/contracts), ping Fraser for help. @@ -125,7 +125,7 @@ If you need help with anything data privacy or [MSA-related](/handbook/growth/sa The [Contracts](/handbook/growth/sales/contracts) page has full guidance on the nuts and bolts of how to put together a commercial proposal - we use PandaDoc. -Don't be the AE who gets to this point and suddently realizes you have no idea who the buyer is! You should already know this, their budget, their purchasing process etc. already as part of your discovery - if you're finding out now, hopefully it's not too late... +Don't be the AE who gets to this point and suddenly realizes you have no idea who the buyer is! You should already know this, their budget, their purchasing process etc. already as part of your discovery - if you're finding out now, hopefully it's not too late... By this point, you may have started running into some objections. These are the most common, and how to handle: diff --git a/contents/handbook/growth/sales/sales-operations.md b/contents/handbook/growth/sales/sales-operations.md index 8d19b1c65ad8..f5b42b9cc0cb 100644 --- a/contents/handbook/growth/sales/sales-operations.md +++ b/contents/handbook/growth/sales/sales-operations.md @@ -22,7 +22,7 @@ If you are looking for guidance on how to manage customers in HubSpot specifical 1. If they are ready to get started with PostHog, we should either: 1. For lower volume customers we should send them a getting started templated email which providers pointers on how to get set up as well as where to get help if they get stuck. 2. For higher volume customers we can create a Slack Connect channel in our Company Slack, this allows us to provide more focused support to ensure that they are successful. -1. As a priority we should get them sending data in from production (even just a small part of thair app) so that they can see the value of PostHog quickly (decreasing time to revenue) see how we do this in the Onboarding section below. +1. As a priority we should get them sending data in from production (even just a small part of their app) so that they can see the value of PostHog quickly (decreasing time to revenue) see how we do this in the Onboarding section below. ## Self-serve Process diff --git a/contents/handbook/people/hiring-process/index.md b/contents/handbook/people/hiring-process/index.md index 772f3aaa6eae..c422b7a62a80 100644 --- a/contents/handbook/people/hiring-process/index.md +++ b/contents/handbook/people/hiring-process/index.md @@ -41,7 +41,7 @@ This has resulted in the highest number of qualified and motivated candidates re ### External recruiters -All of our recruiting is done in-house, and we do not work with external agencies for any of our roles. We frequently receive unsolicited messages from agencies - sometimes 20 in a week - who want to work with us, and the best response is to simply ignore the message. If they attach any candidate profiles or résumés to their email, please _do not_ open the attachment. If you are ever unsure what to do, feel free to forward any unsolicited messages to careers@posthog.com. +All of our recruiting is done in-house, and we do not work with external agencies for any of our roles. We frequently receive unsolicited messages from agencies - sometimes 20 in a week - who want to work with us, and the best response is to simply ignore the message. If they attach any candidate profiles or résumés to their email, please _do not_ open the attachment. If you are ever unsure what to do, feel free to forward any unsolicited messages to careers@posthog.com. ### Deciding to hire @@ -155,7 +155,7 @@ We record all candidate-related comms in Ashby so we can ensure we provide all c Ashby is a pretty intuitive platform to use, but here are a few helpful tips to get you going -* [A guide to getting started with the basics](https://www.notion.so/Getting-Started-for-Interviewers-4b6bd7cc94834e1ebe8d63345030696f) - this is pretty much everything you need to navigate through Ashby to provide feeedback and review candidates. +* [A guide to getting started with the basics](https://www.notion.so/Getting-Started-for-Interviewers-4b6bd7cc94834e1ebe8d63345030696f) - this is pretty much everything you need to navigate through Ashby to provide feedback and review candidates. * Link your Gmail account in Settings if you are in direct contact with candidates - this means any emails you send directly from your inbox will automatically be captured on their Ashby record for everyone on the hiring team to see. * When emailing candidates from within Ashby, you can select a Template from the drop down bar (and customize it if you want). If you find yourself writing the same email, it is worth saving as a template. @@ -244,7 +244,7 @@ In advance of the SuperDay, we will need to do some additional prep to ensure th > We aim to make a decision within 48 hours of SuperDay - being decisive is important at this stage, as great candidates will probably be fielding multiple job offers. -After a SuperDay, everyone involved in the day leaves their feedback on Ashby. This is hugely important to us in making a final decision so team members should make an effort in compeleting their feedback as soon as possible. If there are wildly different opinions, you should open an issue in `company-internal` to discuss. +After a SuperDay, everyone involved in the day leaves their feedback on Ashby. This is hugely important to us in making a final decision so team members should make an effort in completing their feedback as soon as possible. If there are wildly different opinions, you should open an issue in `company-internal` to discuss. If a decision is made to hire, the People & Ops team will open an onboarding issue once the candidate has accepted and James/Tim will share in our Monday All Hands Meeting a brief overview of the following: - Who we ended up hiring and their background: what they will be doing, and a summary of the recruitment process (how long open for, no. of applicants etc.) diff --git a/contents/handbook/product/enterprise-features-prioritization.md b/contents/handbook/product/enterprise-features-prioritization.md index ff06cca5bc4b..2d1a937f6aec 100644 --- a/contents/handbook/product/enterprise-features-prioritization.md +++ b/contents/handbook/product/enterprise-features-prioritization.md @@ -8,7 +8,7 @@ showTitle: true Enterprise features are intended for paying large scale customers (i.e. scale-ups & large enterprises), and generally include features around advanced collaboration and compliance. Enterprise features are used both on Cloud and Self-hosted and could be included in both Scale and/or Enterprise licenses. -PostHog is becoming increasingly used by large corporations who, in general, have different product requirements from hobbyists and startups - particularly around compliance and collaboration. Our milestones for the foreseeable future target improvements around the product rather than these supporting activities. However, we want to make sure these customers can use PostHog unemcumbered, as they're becoming increasingly critical for us. These requirements can usually be seen as important but not urgent (until they are). To make sure we keep delivering on these requirements, we've developed the framework below. +PostHog is becoming increasingly used by large corporations who, in general, have different product requirements from hobbyists and startups - particularly around compliance and collaboration. Our milestones for the foreseeable future target improvements around the product rather than these supporting activities. However, we want to make sure these customers can use PostHog unencumbered, as they're becoming increasingly critical for us. These requirements can usually be seen as important but not urgent (until they are). To make sure we keep delivering on these requirements, we've developed the framework below. Each sprint, we ask the following questions around each requirement. If the answer is "yes" to any of them, we prioritize those for the sprint. If all are "no", we keep them in the backlog. diff --git a/contents/handbook/product/per-product-growth-reviews.md b/contents/handbook/product/per-product-growth-reviews.md index 71801bf3478a..29e705032617 100644 --- a/contents/handbook/product/per-product-growth-reviews.md +++ b/contents/handbook/product/per-product-growth-reviews.md @@ -12,7 +12,7 @@ The objective of the growth review is to review key product metrics and understa Looking at the same metrics regularly will increase our understanding how they relate to each other, whether metric changes are expected or exceptions, and will make efforts to improve them more successful. -The growth reviews should focus on analysing anomalies instead of expected metric behaviour, especially as teams become more familiar with their data. +The growth reviews should focus on analysing anomalies instead of expected metric behavior, especially as teams become more familiar with their data. Outside of the regular meetings, it’s the job of the Product Manager to regularly monitor these metrics, becoming an expert in their nuances. Should a metric deviate from the norm, they are responsible for presenting a well-researched explanation during the review. @@ -35,7 +35,7 @@ We’ve found that the best way to review what is a quite long list of metrics i ### Deep dives -In each growth review, we usually do a couple of deep dives. Topics can be proposed in a preceeding growth review, by team members, or it is simply something the Product Manager finds worthwhile. Here are a couple of examples: +In each growth review, we usually do a couple of deep dives. Topics can be proposed in a preceding growth review, by team members, or it is simply something the Product Manager finds worthwhile. Here are a couple of examples: - Why was churn so high last month? Can we identify any reasons? - Where in the onboarding funnel do new users struggle? @@ -62,7 +62,7 @@ In each growth review, we usually do a couple of deep dives. Topics can be propo ### After the meeting -- PM shares summary of meeting dicussion + outcome with the small team +- PM shares summary of meeting discussion + outcome with the small team - PM makes sure all to dos are completed by the next growth reviews ## Useful material (internal links) diff --git a/contents/handbook/product/product-team.md b/contents/handbook/product/product-team.md index 45f5dfa47674..469fe0c926b1 100644 --- a/contents/handbook/product/product-team.md +++ b/contents/handbook/product/product-team.md @@ -4,8 +4,8 @@ sidebar: Handbook showTitle: true --- -PostHog has a [product-minded engineering organization](/blog/turning-engineers-into-product-people). Engineers own sprint planning and specing out solutions. Read more on the role of the Product Team in this [blog post](/blog/product-at-posthog). +PostHog has a [product-minded engineering organization](/blog/turning-engineers-into-product-people). Engineers own sprint planning and speccing out solutions. Read more on the role of the Product Team in this [blog post](/blog/product-at-posthog). -At the same time, engineering small teams are multidisciplinary and have different focuses within the Product. To support Engineering well, Product and Design are cross-functional too and can work within multiple small teams. Instead of Product Managers (PMs) and Product Designers working on everything a small team works on, they have specific goals that trascend team lines. +At the same time, engineering small teams are multidisciplinary and have different focuses within the Product. To support Engineering well, Product and Design are cross-functional too and can work within multiple small teams. Instead of Product Managers (PMs) and Product Designers working on everything a small team works on, they have specific goals that transcend team lines. PMs or Product Designers fully belong to the relevant small teams (up to 2) so both teams have a strong sense that the person is there to support them both equally in respect to the goals, and to make it clear there are no inter-team dependencies. diff --git a/contents/tutorials/android-session-replay.md b/contents/tutorials/android-session-replay.md index b63f692d289d..9096e3f2d680 100644 --- a/contents/tutorials/android-session-replay.md +++ b/contents/tutorials/android-session-replay.md @@ -131,7 +131,7 @@ class WelcomeActivity : AppCompatActivity() { } ``` -Lastly, go to the `manifests` directory and add your new activities to `AndroidManifext.xml`: +Lastly, go to the `manifests` directory and add your new activities to `AndroidManifest.xml`: ```xml file=AndroidManifest.xml diff --git a/contents/tutorials/anthropic-analytics.md b/contents/tutorials/anthropic-analytics.md index d3e367d65f76..81925409103a 100644 --- a/contents/tutorials/anthropic-analytics.md +++ b/contents/tutorials/anthropic-analytics.md @@ -257,7 +257,7 @@ To create this insight, go the [Product analytics tab](https://us.posthog.com/in 1. Set the event to `claude_message_completion` 2. Click on **Total count** to show a dropdown. Click on **Property value (sum)**. 3. Select the `total_cost_in_dollars` property. -4. Cclick **+ Add breakdown** and select `model` from the event properties list. +4. Click **+ Add breakdown** and select `model` from the event properties list. > **Note:** Insights may show `0` if the total cost is less than `0.01`. diff --git a/src/components/People/index.tsx b/src/components/People/index.tsx index 1d132217ad96..604d5ffc8551 100644 --- a/src/components/People/index.tsx +++ b/src/components/People/index.tsx @@ -84,7 +84,7 @@ export default function People() { const teamSize = teamMembers.length - 1 - // Some Stats were used as fallback until the actual data is added to the GraphlQL Server + // Some Stats were used as fallback until the actual data is added to the GraphQL Server const teamStats = [ { data: pineappleOnPizzaStat(teamMembers) ? pineappleOnPizzaStat(teamMembers) : [60, 40], diff --git a/src/components/Pricing/PricingCalculator/Tabs/ProductAnalytics.tsx b/src/components/Pricing/PricingCalculator/Tabs/ProductAnalytics.tsx index 9d7ee0db2746..63f059e2fc9e 100644 --- a/src/components/Pricing/PricingCalculator/Tabs/ProductAnalytics.tsx +++ b/src/components/Pricing/PricingCalculator/Tabs/ProductAnalytics.tsx @@ -193,7 +193,7 @@ const Modal = ({ onClose, isVisible }) => { .

- Indentify users by their email address or other unique identifier, and attach custom + Identify users by their email address or other unique identifier, and attach custom properties to their person profiles.

diff --git a/src/components/Pricing/PricingExperiment.tsx b/src/components/Pricing/PricingExperiment.tsx index 2f693b53da11..469894bf8839 100644 --- a/src/components/Pricing/PricingExperiment.tsx +++ b/src/components/Pricing/PricingExperiment.tsx @@ -408,7 +408,7 @@ const ProductTabs = ({ billingProducts }) => {
{activeTab == undefined && (

- *Free tier resets monthly. Prices descrease exponentially with volume. + *Free tier resets monthly. Prices decrease exponentially with volume.

)} diff --git a/src/components/Product/FeatureFlags/index.tsx b/src/components/Product/FeatureFlags/index.tsx index c4dcf6835bba..aa4cab50f29a 100644 --- a/src/components/Product/FeatureFlags/index.tsx +++ b/src/components/Product/FeatureFlags/index.tsx @@ -59,7 +59,7 @@ const featuresPerRow = 3 const features = [ { title: 'Release conditions', - description: 'Customize your rollout strategy by user or group properties, cohort, or trafic percentage', + description: 'Customize your rollout strategy by user or group properties, cohort, or traffic percentage', image: , border: true, }, diff --git a/src/components/Startups/index.tsx b/src/components/Startups/index.tsx index 263f5345e23a..c27fc9eb6de0 100644 --- a/src/components/Startups/index.tsx +++ b/src/components/Startups/index.tsx @@ -200,7 +200,7 @@ export default function Startups() { name: 'raised', type: 'enumeration', options: [ - { label: 'Boostrapped', value: 0 }, + { label: 'Bootstrapped', value: 0 }, { label: 'Under $100k', value: 100_000 }, { label: '$100k - $500k', value: 500_000 }, { label: '$500k - $1m', value: 1_000_000 }, @@ -210,7 +210,7 @@ export default function Startups() { required: true, }, { - label: 'The date that your company was incorportated', + label: 'The date that your company was incorporated', name: 'incorpation_date', type: 'string', fieldType: 'date', diff --git a/src/pages/docs/product-analytics.tsx b/src/pages/docs/product-analytics.tsx index 11c3552fb2a5..ee727a29a2c4 100644 --- a/src/pages/docs/product-analytics.tsx +++ b/src/pages/docs/product-analytics.tsx @@ -161,7 +161,7 @@ export const Content = ({ quickLinks = false }) => {
  • Ashby allows PostHog to search various databases which may include your personal data - (including your CV or Résumé), to find possible candidates to fill our job openings. + (including your CV or résumé), to find possible candidates to fill our job openings. Where we find you in this way, we will obtain your personal data from these sources.
  • diff --git a/src/templates/merch/Product.tsx b/src/templates/merch/Product.tsx index 48e1610cebf7..716c2735dcfe 100644 --- a/src/templates/merch/Product.tsx +++ b/src/templates/merch/Product.tsx @@ -48,7 +48,7 @@ export default function Product(props: ProductPageProps): React.ReactElement { /** * The product.variant option from props is a different shape from the - * slectedVariant (which comes directly from the Storefront API). We + * selectedVariant (which comes directly from the Storefront API). We * only want the ID from selectedVariant and will add the corresponding * variant in product.variants. */ diff --git a/src/templates/merch/ProductPanel.tsx b/src/templates/merch/ProductPanel.tsx index 91072bb50604..4b05239d9151 100644 --- a/src/templates/merch/ProductPanel.tsx +++ b/src/templates/merch/ProductPanel.tsx @@ -35,7 +35,7 @@ export function ProductPanel(props: ProductPanelProps): React.ReactElement { /** * The product.variant option from props is a different shape from the - * slectedVariant (which comes directly from the Storefront API). We + * selectedVariant (which comes directly from the Storefront API). We * only want the ID from selectedVariant and will add the corresponding * variant in product.variants. */