Fix typos in www-gitlab-com entire project

source/handbook/anti-harassment/index.html.md

@@ -40,7 +40,7 @@ Sexual harassment encompasses a wide range of conduct, examples of misconduct in
 1. Creating displays, communications, or publications including content of a sexually offensive nature.
 1. Purposely misgendering people, consistently referring to someone as 'he' after repeated requests to call someone a 'she' or vice versa.  
-Sexual harrassment is considered a form of team member misconduct and sanctions will be enforced against individuals engaging in sexual harrassment and against supervisory and managerial personnel who knowingly allow such behaivor to continue.  Any retaliation against an individual who complain of sexual harrassment or who testify or assist in any proceeding under the law is unlawful.  
+Sexual harassment is considered a form of team member misconduct and sanctions will be enforced against individuals engaging in sexual harassment and against supervisory and managerial personnel who knowingly allow such behavior to continue.  Any retaliation against an individual who complain of sexual harassment or who testify or assist in any proceeding under the law is unlawful.  
 ### Discrimination

source/handbook/board-meetings/index.html.md

@@ -22,8 +22,8 @@ title: "Board of Directors and Governance"
 1. Final draft presentations are due one week prior to the meeting.
 1. Board materials are distributed the friday before the meeting.
 1. There will be two deep dives on the agenda for each board meeting:
-    - 30 minutes alotted to a single functional area (i.e. sales, marketing, engineering, product, g&a, etc) on a rotation basis
-    - 30 minutes alotted to a topic(s) of strategic or operational importance to the Company.
+    - 30 minutes allotted to a single functional area (i.e. sales, marketing, engineering, product, g&a, etc) on a rotation basis
+    - 30 minutes allotted to a topic(s) of strategic or operational importance to the Company.
 1. Discussion points are clearly marked, each get a time allotment, five minutes unless otherwise approved.
 1. Board members are assumed to have studied the materials.
 1. For now the whole executive team is present during the meeting.

source/handbook/business-ops/data-team/index.html.md

@@ -507,7 +507,7 @@ We use the repository-syntax instead of the hub-syntax in [our `packages.yml` fi
 ### dbt test coverage rotation
-Occassionally `dbt test` may produce failures. 
+Occasionally `dbt test` may produce failures. 
 Many of these failures are upstream data quality problems that need to be addressed. 
 In order to have clear responsibility for test failures, the data team has implemented a responsibility chart that takes advantage of folks native timezones. 
 This helps address the bystander effect. 

source/handbook/business-ops/index.html.md

@@ -82,7 +82,7 @@ The team member who is putting on the planning hat is *not* responsible for:
 ## Tech Stack
-#### Tech Stack Support Heirarchy
+#### Tech Stack Support Hierarchy
 1. System Owners
 1. IT Operations or People Operations
@@ -362,7 +362,7 @@ System owners will remain the point of contact for provisioning and issues invol
   <tr>
     <td><strong><a href="/handbook/business-ops/tech-stack/#visual-compliance">Visual Compliance (Link to come)</a></strong></td>
     <td>Access via Salesforce</td>
-    <td><strong>Jamie Hurewitz (primary)</strong><br>Related to Technical Implementaion: Michael Snow (secondary)</td>
+    <td><strong>Jamie Hurewitz (primary)</strong><br>Related to Technical Implementation: Michael Snow (secondary)</td>
     <td>Michael Snow</td>
   </tr>
   <tr>
@@ -774,31 +774,31 @@ Sales Segmentation is based on `Total Employee` count of the `Global Account`.
   * `Mid-Market` = 100-1,999 total employees
   * `SMB` (Small Business) = 0-99 total employees
-`Total Employee` count is based on the number of employees that our data tools return for that account. We use a hierachy structure to determine what the number of employees is for the account. The hierarchy of our data tools on *Accounts* as they relate to the `Total Employee` count is shown below.
+`Total Employee` count is based on the number of employees that our data tools return for that account. We use a hierarchy structure to determine what the number of employees is for the account. The hierarchy of our data tools on *Accounts* as they relate to the `Total Employee` count is shown below.
 1. DataFox.......(Default Value)
 2. DiscoverOrg...(Only used if DataFox Employee Count field is blank)
 LinkedIn/Websites are not designated data sources. If a prospect communicates a different employee size from DataFox/DiscoverOrg that conflicts with segmentation of what is determined by DataFox/DiscoverOrg than SalesOPS should be notified via chatter on the record. Admins have the ability to override the `Number of Employees` and bypass this hierarchy but only during our [sales segment review process](#Sales-Segment-Review-Process)
-#### Sales Segment and Hierachy Review Process
+#### Sales Segment and Hierarchy Review Process
 In order to address issues when it is believed that the `Total Employee` count is incorrect the Sales Ops team on a Yearly schedule(TBD) will review accounts where individuals think that the segment is incorrect. Reviews for updates to the `Total Employee` count field that do not result in a change of segment will not be reviewed.
 For an individual to submit an account for review as it relates to the number of employees at the account they must fill out the following two fields on an accounts:
 * `Number of Employees: Manual - User` - This is a number field that you think the number of employees should be
-* `Number of Employees: Manual Source -User` - This is a url field that links to where the above infromation was found
+* `Number of Employees: Manual Source -User` - This is a url field that links to where the above information was found
 For an individual to submit an account for review as it relates to the hierarchy and final address of the account they must fill out the following four fields on an account:
 *  `Account Zip - Manual - User` - This is a text field to be populated with Global Account HQ's Zip
 *  `Account State - Manual - User` - This is a text field to be populated with Global Account HQ's State
 *  `Account Country - Manual - User` - This is a text field to be populated with Global Account HQ's Country
-*  `Account Address - Manual Source - User` - This is a url field that links to where the above infromation was found
+*  `Account Address - Manual Source - User` - This is a url field that links to where the above information was found
 Examples of valid sources include but are not limited to financial filings, newspaper articles, reports directly from the company. As a rule LinkedIn is not accepted as a valid source. During the Sales Ops review period it is at the discretion of the Sales Ops team to have the `Total Employee` count updated or to have it remain the same.
 ### Region/Vertical
-  * **VP Commerical Sales** (Mid-Market & Small Business): Ryan O'Nell
+  * **VP Commercial Sales** (Mid-Market & Small Business): Ryan O'Nell
   * **[Europe, Middle East and Africa](#emea)**: Richard Pidgeon, Regional Director
   * **[North America - US East](#us-east)**: Mark Rogge, Regional Director
   * **[North America - US West](#us-west)**: Haydn Mackay, Regional Director
@@ -993,7 +993,7 @@ For other countries in NORAM, governments agencies will be handled by the territ
 These maps were created using [MapChart](https://mapchart.net/). The txt files to make future updates can be found in `images/handbook/business-ops/map-txt-files` directory. Please do not edit these files unless you are Sales or Markting OPS.
-In Marketo we have modified the country values to match Salesforce to allow for seamless syncronization between the two systems. When creating new forms in Marketo, you can use the "Master Country List" (viewable on the Google Drive), copying column A into the form builder.
+In Marketo we have modified the country values to match Salesforce to allow for seamless synchronization between the two systems. When creating new forms in Marketo, you can use the "Master Country List" (viewable on the Google Drive), copying column A into the form builder.
 ### Account Ownership Rules of Engagement
@@ -1001,7 +1001,7 @@ In Marketo we have modified the country values to match Salesforce to allow for
 2. **Account Ownership**: Will be determined by the **Ultimate Parent Account** `Segment`, `Address` and `Corporate Hierarchy` and all children accounts, regardless of physical location. All of the accounts will be owned by the *Global Account* owner unless it is either a Named Account (see point 3) or it has been agreed upon by both reps and their managers that the customer is best serviced by the *Territory* rep (see point 12).
 3. **Named Account**: Defined as an account that is owned by a sales rep regardless of corporate headquarters. A sales rep will own no more than 30 named accounts.
 4. **Transfer of Named Accounts**: A transfer and ownership time frame of a Named Account should be agreed upon by both sales reps and their managers. This should be documented in the Account Transition MASTER document (found in Google drive).
-5. **Open Opportunities of Transferred Accounts**: Any open opportunity on an account subject to transfer to the *global account* owner will remain with the original owner for a period of no more than 180 days after opportunity creation. No later than the 120 day mark, the original owner can request an extension and must provide sufficient evidence that the deal will close within the next 90 days. If the evidence is insufficient, the *global account* owner can request that the opportunity be transferred immediately. These opportunites will be tracked in the Account Transition MASTER document (found in Google drive).
+5. **Open Opportunities of Transferred Accounts**: Any open opportunity on an account subject to transfer to the *global account* owner will remain with the original owner for a period of no more than 180 days after opportunity creation. No later than the 120 day mark, the original owner can request an extension and must provide sufficient evidence that the deal will close within the next 90 days. If the evidence is insufficient, the *global account* owner can request that the opportunity be transferred immediately. These opportunities will be tracked in the Account Transition MASTER document (found in Google drive).
 6. **Reassigning to a Territory Rep**: The *global account* owner can reassign any child account to a *territory rep* if it is determined that the client/prospect would be best serviced by a local rep. To do this, please Chatter the *territory rep* and provide an explanation on the transfer. Please review point 12 'Considerations for Transferring an Account to a Local Rep'.
 7. **Requesting Reassignment**: A *territory rep* can request reassignment of a child account if he/she feels that the client/prospect would be best serviced by a territory rep as opposed to the *global account owner*. To do this, the *territory rep* must Chatter the *global account* owner and provide an explanation, (please see point 12, “Considerations for Transferring an Account to a Local Rep”). It is at the discretion of the *global account* owner to keep or reassign the account, but they must provide a compelling and explicit reason why a *territory* account should be managed globally. If the *territory rep* does not agree with the decision, it can be discussed by their respective managers.
 8. **Parent/Child Segmentation**: All Accounts in a hierarchy will adopt the highest Segmentation of any account in the hierarchy.
@@ -1025,7 +1025,7 @@ Status in the table below means:
 | Source                          | Definition and/or transition plan                                                                            | Status*  |
 |:--------------------------------|:-------------------------------------------------------------------------------------------------------------|:---------|
-| Advertisment                    | to be evaluated                                                                                              | Active   |
+| Advertisement                   | to be evaluated                                                                                              | Active   |
 | AE Generated                    | Sourced by an Account Executive through networking or professional groups                                    | Active   |
 | CE Download                     | Downloaded CE version of GitLab                                                                              | Active   |
 | CE Usage Ping                   | Created from CE Usage Ping data                                                                              | Active   |
@@ -1066,7 +1066,7 @@ Status in the table below means:
 | Owned Event                     | Events that are created, owned, run by GitLab                                                                | Active   |
 | Partner                         | GitLab partner sourced name either through their own prospecting and/or events                               | Active   |
 | Promotion                       | to be evaluated                                                                                              | Active   |
-| Prospecting                     | Account research and developement prospecting work                                                           | Pending  |
+| Prospecting                     | Account research and development prospecting work                                                           | Pending  |
 | Prospecting - LeadIQ            | transition to `Prospecting` -> sub field `LeadIQ`                                                            | Active   |
 | Public Relations                | to be evaluated                                                                                              | Active   |
 | Referral                        | to be evaluated                                                                                              | Inactive |
@@ -1228,7 +1228,7 @@ ACCOUNT/CONTACT records in Salesforce are created in a number of ways - [list im
         - The `Initial Source` on a CONTACT record *does not* equal `Source` on an opportunity. Refer to [`Initial Source`](#initial-source) for guidance on why this is important.
    - Record **does** exist:
         - If LEAD or CONTACT is unowned or "owned by Sales Admin, JJ Cordz, Francis Aquino or Chad Malchow", this record is adoptable by anyone - change `Record Owner` to your name
-        - If LEAD or CONTACT is owned by BDR team member, **before** reaching out Chatter on the record asking BDR to transfer ownership. Ownership *must* be transfered **before** reaching out to avoid confusion, cross-communication and/or multiple people reaching out to same contact.
+        - If LEAD or CONTACT is owned by BDR team member, **before** reaching out Chatter on the record asking BDR to transfer ownership. Ownership *must* be transferred **before** reaching out to avoid confusion, cross-communication and/or multiple people reaching out to same contact.
 When official event list import is completed the created ACCOUNT or CONTACT record will be appended with the additional data collected at the event. If there are any questions or you need assistance, please ping Marketing or Sales OPS in Slack `#sfdc-users` channel.
@@ -1505,7 +1505,7 @@ The following criteria is required for an XDR (SDR or BDR) to submit an opportun
 **Authority**
 The prospect being met is directly involved in a project or team related to the potential purchase of GitLab within this buying group, either as an evaluator, decision maker, technical buyer, or *influencer.
-*If the “influencer” is not directly involved (i.e. is related to a "decision maker" in another group/division or someone who is not directly tied to the opportunity at hand) the XDR will continue to own the opportunity and will seek to set-up the next meeting with a key contact in the buying group (leaving 0-pending status until date/referral is confirmed), updating the current opportunity with the new directly-involved point of contact in the buying group once it's aquired.
+*If the “influencer” is not directly involved (i.e. is related to a "decision maker" in another group/division or someone who is not directly tied to the opportunity at hand) the XDR will continue to own the opportunity and will seek to set-up the next meeting with a key contact in the buying group (leaving 0-pending status until date/referral is confirmed), updating the current opportunity with the new directly-involved point of contact in the buying group once it's acquired.
 **Initiative**
 An initiative the company is working on has been identified and GitLab can potentially help the initiative. Identified by either a business problem (i.e too many tools), strategic direction or modernization interest (impetus to change).
@@ -1520,7 +1520,7 @@ The following fields have been obtained:
 After the initial qualifying meeting with the account leader/executive, there must be a next step that is set to occur within a *60 day timeframe. (*If next step isn’t within a 60 day timeframe, the opportunity remains in stage 0 and in XDR ownership to nurture until the next step is actualized.)
 _**XDR best practice:**_
-Ask prospect about their enviroment, what they develop software for etc. to try build a picture of the company and how we will be able to help them
+Ask prospect about their environment, what they develop software for etc. to try build a picture of the company and how we will be able to help them
 Share relevant resources with the point of contact
 Add other potential influencers/buyers from that company into our database and the Outreach cadence in an effort to build more momentum within that organization.
@@ -1839,7 +1839,7 @@ To help move sales through the sales process, [here](https://docs.google.com/doc
 Note that once you qualify an opportunity via our standard qualification process, you cannot revert an opportunity back to the following stages: `00-Pre Opportunity`, `0-Pending Acceptance`, or `9-Unqualified`. If you need to revert an opportunity you've previously qualified to one of these stages, please contact Sales Operations and we can determine why the opportunity (once qualified) is no longer qualified.
 #### Reverting an Opportunity to a Previous Stage
-If a previously met criteria has become unmet, you are required to revert back to the latest stage where all activites were completed. For example, if a prospect had previously signed off on GitLab from a technical standpoint, requested a quote and has begun contract negotiations, you would set the opportunity to `5-Negotiating`. However, if at any point during the negotiations, additional technical questions or requirements arise that result in a re-evaluation of GitLab's technical capabilities, you would revert the opportunity back to `3-Technical Evaluation`. After the opportuniy has once again met the stage completion criteria, you are able to move the opportunity to either `4-Proposal` if a new order form was created as a result of the additional technical requirements, or back to `5-Negotiating` if no changes were made to the original order form.
+If a previously met criteria has become unmet, you are required to revert back to the latest stage where all activities were completed. For example, if a prospect had previously signed off on GitLab from a technical standpoint, requested a quote and has begun contract negotiations, you would set the opportunity to `5-Negotiating`. However, if at any point during the negotiations, additional technical questions or requirements arise that result in a re-evaluation of GitLab's technical capabilities, you would revert the opportunity back to `3-Technical Evaluation`. After the opportuniy has once again met the stage completion criteria, you are able to move the opportunity to either `4-Proposal` if a new order form was created as a result of the additional technical requirements, or back to `5-Negotiating` if no changes were made to the original order form.
 ### Locking Opportunities as a result of their "At Risk" potential
 In order to be in compliance with US Regulations there is a need to screen opportunities against known individuals and organizations who we should not be selling to. In order to meet these regulations opportunities are screened when they are created through a third party application, Visual Compliance. If an opportunity triggers any Red Flags it will be locked until it is reviewed by our legal team and it is deemed that it is okay to move forward with the opportunity.

source/handbook/business-ops/order-processing/index.html.md

@@ -239,7 +239,7 @@ According to [our matrix](https://docs.google.com/document/d/1-CH-uH_zr0qaVaV1Qb
 *  Once a user submits a quote for approval it follows the order of approvers as stated in our approvers matrix.
 *  When you are requiered to review a quote and are the current team member who should review a quote you will be notified by email. In the email you will find the details as to why your approval, who any previous approvers were as well as a link directly to the quote.
 *  Once you have reviwed the quote you can either approve or reject any quote in one of two ways. 
-   1.  You can reply directly in the email that you recieved by following the instruction in the email as to if you approve or reject the quote
+   1.  You can reply directly in the email that you received by following the instruction in the email as to if you approve or reject the quote
    2.  You can approve or reject the quote directly within salesforce on the bottom of the quote page under `Approval History`
 * If you are going to be unavailable to review and approve quotes (PTO, at a conference etc.) please coordinate with the appropriate team members to ensure that there will still be someone who can review quotes while you are unavailable. 
    
@@ -621,7 +621,7 @@ This requires two steps: first combining the subscriptions, then cancelling the
 The following events will trigger require the Churn Information to be completed on the opportunity record:
 * An opportunity has been submitted for approval with a negative amount. This signifies either a credit or refund of a subscription was requested by a customer and processed by an Account Executive or Account Manager.
-* A renewal opportunity has been won, but has a negative IACV. This signfies that the customer has downgraded. Sales Operations and Finance will reach out to the opportunity owner to understand the nature of the churn.
+* A renewal opportunity has been won, but has a negative IACV. This signifies that the customer has downgraded. Sales Operations and Finance will reach out to the opportunity owner to understand the nature of the churn.
 * A renewal opportunity has been lost. This signifies that the customer did not renew their subscription. Sales Operations and Finance will reach out to the opportunity owner to understand why the customer did not wish to renew.The following information will be captured:
 When one of the above conditions are met, the user is responsible for entering the following details on the Churn Information of the opportnity record:
@@ -692,7 +692,7 @@ With GitLab's announcement that our Ultimate and Gold packages will be free for
 9. Select the Account you'd like to associate to Quote to
 10.Select "New Subscription for this Account"
 11. Click "Next"
-12. In the Quote Template, select "Ultimate or Gold Free (OSS Only)" for OSS organizations and "Ultimate or Gold Free (EDU Only)" for educational institutions (the difference between the templates is becuase of an additional addendum for EDU)
+12. In the Quote Template, select "Ultimate or Gold Free (OSS Only)" for OSS organizations and "Ultimate or Gold Free (EDU Only)" for educational institutions (the difference between the templates is because of an additional addendum for EDU)
 13. Click "Primary"
 14. Add a Sold to and Bill To Contact
 15. Enter the Start Date

source/handbook/business-ops/sfdc/index.html.md

@@ -10,14 +10,14 @@ title: "Business Operations - Salesforce Reference"
 {:toc}
 ## Purpose
-The purpose of this page is to provide insight into the internal workings of our Salesforce (SFDC) instance, how fields are populated, how fields are calcualted, where they are used etc. This page does not serve to describe how the systems should be used by our internal stake holders. Instead it is meant to be used as a reference point for continual development by our internal ops teams as well as a reference point for all Gitlabbers as to the source of the information that is shown within SFDC. The goal of this document is not to document every field that exists within SFDC but instead to highlight the hidden process that affect fields that meet 1 or more of the following criteria  
+The purpose of this page is to provide insight into the internal workings of our Salesforce (SFDC) instance, how fields are populated, how fields are calculated, where they are used etc. This page does not serve to describe how the systems should be used by our internal stake holders. Instead it is meant to be used as a reference point for continual development by our internal ops teams as well as a reference point for all Gitlabbers as to the source of the information that is shown within SFDC. The goal of this document is not to document every field that exists within SFDC but instead to highlight the hidden process that affect fields that meet 1 or more of the following criteria  
 1. The main fields that are leveraged by the teams (Ex: IACV) 
 1. Fields that are updated via automation rules (Ex: Sales Segmentation) 
 1. Fields that are sourced from other systems (Ex: DiscoverOrg ID vs id)
 ### Structure of this Document
-The structure and sequence of infromation in this document will follow these guidlines: 
+The structure and sequence of information in this document will follow these guidlines: 
 ## SFDC Object
 ### SFDC Object - SFDC Field
 * Description: What is the information in this field
@@ -39,7 +39,7 @@ The structure and sequence of infromation in this document will follow these gui
 ### Account - Total Account Value
 * Description: This field aims to capture the dollar value that an account has committed to us. It sums the `Amount` field on all opportunities that meet the following criteria. They are all not deleted as well as they are ((Any closed won Opp that is `New Business` OR `Renewal`) OR (Any open `Renewal` Opp))
 * Populating: Via a Rollup Helper Rollup
-* Use: This field is used to help calcualte Gemstone types
+* Use: This field is used to help calculate Gemstone types
 ### Account - CMRR All Child Accounts
 * Description: This field sums all of the CMRR amounts from all of an accounts child records. Its source field is `CMRR This Account`. The filter used is to sum only the `CMRR This Account` amounts that are from Accounts that are `Type`:`Customer`.
@@ -124,7 +124,7 @@ The structure and sequence of infromation in this document will follow these gui
 * Use:  
 ### Opportunity - Count of Professional Services Opportunities
-* Description: This field counts the number of Professional Services Opportunities that are assocaited with this Opporutnity. Opportunities are only included in this count if they are not deleted, their opportunity `Record Type` is `Professional Services` (based on the record type ID) and the Opportunity is the `Parent Opportunity` for that opportunity
+* Description: This field counts the number of Professional Services Opportunities that are associated with this Opporutnity. Opportunities are only included in this count if they are not deleted, their opportunity `Record Type` is `Professional Services` (based on the record type ID) and the Opportunity is the `Parent Opportunity` for that opportunity
 * Populating: Via a Rollup Helper Rollup
 * Use:  

source/handbook/business-ops/tech-stack/index.html.md

@@ -157,7 +157,7 @@ You can schedule somone to be placed on "vacation hold" in a round robin group.
 10. The system will automatically pull this person out of the round robin during this period and add them back in when the vacation hold has expired. 
 ## Marketo  
-Marketo is our marketing automation platform managed by our Marketing Ops team. Anyone who signs up for a trial, requests contact from GitLab, attends a webinar or trade show, or engages in any other marketing activity, will end up in Marketo. These prospects will receive scores based on their level of engagement and these scores will be used by the Business Developement Representatives and Account Executives to prioritize which prospects to follow up with. Marketo is also our primary tool for delivering marketing communication to prospects and customers.  
+Marketo is our marketing automation platform managed by our Marketing Ops team. Anyone who signs up for a trial, requests contact from GitLab, attends a webinar or trade show, or engages in any other marketing activity, will end up in Marketo. These prospects will receive scores based on their level of engagement and these scores will be used by the Business Development Representatives and Account Executives to prioritize which prospects to follow up with. Marketo is also our primary tool for delivering marketing communication to prospects and customers.  
 ## Moz Pro  

source/handbook/ceo/pricing/index.html.md

@@ -329,6 +329,6 @@ As suggested by [a user on Twitter](https://twitter.com/javierfeldman/status/110
 This is a good suggestion to consider given the GitLab approach to adapting to local markets throughout the business.  GitLab will assess viability of the idea in our overall pricing strategy planning.  It is difficult to do and our assessment of this will consider:
 1. This is a complex issue and requires that all parties are better off if a change is made to account for geography.  We fully admit that this would be hard to pull off successfully.
 1. If there is a way this could be good for customers and for GitLab, we will not treat this separately.  We will treat it as part of a unified pricing strategy
-1. In a global and digital marketplace it is difficult to positively identify where a customer is geographically located either becuase we rely on that customer to self-identify or becuase it is a large organization with users in several geographical locations.
+1. In a global and digital marketplace it is difficult to positively identify where a customer is geographically located either because we rely on that customer to self-identify or because it is a large organization with users in several geographical locations.
 1. We may be able to solve with a simpler discounting policy
 1. Any overall reduction in cost per license must be more than made up by increased volume at the new pricing

source/handbook/ceo/shadow/index.html.md

@@ -179,7 +179,7 @@ You are eligible to apply for the program if you havev accepted an offer at GitL
 ## Expenses, travel and lodging
-Lodging during the CEO shadow program is provided by the company. CEO executive assistant books the accomodation based on availability and cost. You can express your preference (hotel or AirBnB) via email to the EA in question, however the final decision is made by the EA based on the distance from CEO and costs. EA will provide the accomodation details no earlier than 1 month and no later than 2 weeks before the scheduled rotation.
+Lodging during the CEO shadow program is provided by the company. CEO executive assistant books the accommodation based on availability and cost. You can express your preference (hotel or AirBnB) via email to the EA in question, however the final decision is made by the EA based on the distance from CEO and costs. EA will provide the accommodation details no earlier than 1 month and no later than 2 weeks before the scheduled rotation.
 Accommodation is provided only for the active shadowing period, it is not provided during the shadow program pause (cases when the CEO is unavailable).
 In case you are coming from a timezone that is more than 6 hours difference with Pacific Time, it is possible to book the weekend before the first shadow work day to adjust to the new timezone.
@@ -240,7 +240,7 @@ The wireless mouse and keyboard are connected to the middle, bottom TV by defaul
 ### Office Preparation Guide
-In preperation for guests (customers, investors, etc.) who will be meeting with Sid at the Boardroom, please note the following prior to the meeting start:
+In preparation for guests (customers, investors, etc.) who will be meeting with Sid at the Boardroom, please note the following prior to the meeting start:
 1. All Gitlabbers sit on one side. This allows for easy communication to the guests
 1. Have drinks available on table (from the fridge)

source/handbook/contracts/index.html.md.erb

@@ -127,9 +127,9 @@ CXC will hire individuals as casual employees with an initial contract of two ye
 CXC will hire individuals as T4 Workers, paid on an hourly basis each fortnight. Time-sheets are required to be completed and submitted to CXC. These are to comply with the public holiday paid time off requirements and vacation pay accrual that is credited to the individuals account. In addition to the paid vacation as stated in CXC's contract, further details are also provided in a separate letter.
 1. Offer is made by the manager/recruiter per the [hiring process](/handbook/hiring).
-1. The Canidate Experience Specialist emails the new team memeber the Contract Info Request - Canada from GreenHouse.
+1. The Canidate Experience Specialist emails the new team member the Contract Info Request - Canada from GreenHouse.
 1. The Canidate Experience Specialist will complete the CXC Global Project Information sheet. This is located on the Google Drive: Employee and Contractor Templates and Staging => CXC Canada Folder.
-1. Once that sheet is completed post in the peopleops confidential slack channel for approval. (unless it is for a People Ops team memeber)
+1. Once that sheet is completed post in the peopleops confidential slack channel for approval. (unless it is for a People Ops team member)
 1. Email the sheet to CXC Canada contact (see Australia section above for location of contact details). CXC will then prepare the SOW for signatures.
 1. Once the SOW has been sent back to recruiter or people ops rep, stage for signature in DocuSign and then send back to CXC who will then prepare the contract
 1. Kindly allow a duration of one week for CXC to complete their process. This might mean that a two week notice period to start at GitLab, could increase to three weeks, its important to communicate this duration to new hires in this location.

source/handbook/customer-success/comm-sales/index.html.md

@@ -19,7 +19,7 @@ The Commercial Sales segment is supported by a dedicated team of Solutions Archi
 - TOC
 {:toc}
-## Role & Responsiblities
+## Role & Responsibilities
 ### Solutions Architects
 * SA’s are aligned to the Commercial Sales Reps by a pooled model. Requests for an SA will be distributed between the SA's based on multiple factors including availability, applicable subject matter expertise, and workload.  

source/handbook/customer-success/professional-service-engineering/workflows/artifacts/after-action.html.md

@@ -12,7 +12,7 @@ The following reports are templates to be filed after a particular activity take
 - TOC
 {:toc}
-This report tempalte should be used for
+This report template should be used for
 * On-Site After Action Reports
 * Go-Live After Action Report
 * Training After Action Report

source/handbook/customer-success/solutions-architects/index.html.md

@@ -16,7 +16,7 @@ SA's identify and propose comprehensive solutions to complex business problems a
 - TOC
 {:toc}
-## Role & Responsiblities
+## Role & Responsibilities
 See the [Solutions Architect role description](/job-families/sales/solutions-architect/)

source/handbook/customer-success/tam/index.html.md

@@ -54,7 +54,7 @@ All Premium customers with a minimum Annual Recurring Revenue (ARR) of $100,000
 * Account healthchecks
 * Quarterly business reviews
 * Success strategy roadmaps - beginning with a 30/60/90 day success plan
-* To act as a key point of contact for guidance, advice and as a liason between the customer and other GitLab teams
+* To act as a key point of contact for guidance, advice and as a liaison between the customer and other GitLab teams
 * Own, manage, and deliver the customer onboarding experience
 * Help GitLab's customers realize the value of their investment in GitLab
 * GitLab Days

source/handbook/customer-success/tam/onboarding/index.html.md

@@ -38,7 +38,7 @@ Once an account has been assigned to a Technical Account Manager, they must open
 This project is internal only (not customer-facing) and is to help and guide Technical Account Managers in working through their customer onboarding properly with each customer. It also provides a platform for communication outside of Salesforce to pull in other members of the GitLab team for discussion if needed. You must complete all tasks within the issue in order to close it, and the onboarding object in Salesforce cannot be closed until this issue is completed. Do not skip steps. If you need help, please ask your leader and your team for support and guidance.
-The onboarding object must be completed in parrallel to the issue as Salesforce is our single source of truth and the fields in the object can be reported upon for historical context and metrics.
+The onboarding object must be completed in parallel to the issue as Salesforce is our single source of truth and the fields in the object can be reported upon for historical context and metrics.
 The onboarding object status and date time-box must be updated as quickly as possible upon account assignment. This is important for reporting purposes. 

source/handbook/customer-success/tam/triage/index.html.md

@@ -107,7 +107,7 @@ With the description populated, the milestone should be assigned to the quarterl
 * At least two major releases behind.
 * Frequently don't show up or are late to scheduled cadence calls.
 * Raises more than 15 tickets a month.
-* Customer was aquired and parent company uses competitor.
+* Customer was acquired and parent company uses competitor.
 * Negative NPS scores.
 **Yellow**
@@ -135,7 +135,7 @@ With the description populated, the milestone should be assigned to the quarterl
 * Up to date on releases.
 * Raises between 1 and 5 tickets a month and regularly contributes to issues.
 * Regularly provides feedback on how to improve GitLab.
-* Postive NPS scores.
+* Positive NPS scores.
 #### Triage Labels for at risk (~red) accounts

source/handbook/documentation/index.html.md

@@ -59,7 +59,7 @@ For more information, see the [Documentation section of our Development docs](ht
    - [Documentation workflow](https://docs.gitlab.com/ee/development/documentation/workflow.html)
    - [Documentation page structure and template](https://docs.gitlab.com/ee/development/documentation/structure.html)
    - [Documentation Style Guide](https://docs.gitlab.com/ee/development/documentation/styleguide.html)
-   - [Documentaion site architecture](https://docs.gitlab.com/ee/development/documentation/site_architecture/index.html)
+   - [Documentation site architecture](https://docs.gitlab.com/ee/development/documentation/site_architecture/index.html)
 - The [Documentation Markdown Guide](https://about.gitlab.com/handbook/product/technical-writing/markdown-guide/)
 - The [GitLab Docs project](https://gitlab.com/gitlab-com/gitlab-docs/) which contains the code that pulls the documentation content from multiple repositories and builds docs.gitlab.com

source/handbook/ea/index.html.md

@@ -86,7 +86,7 @@ The public process does two things: allows others to benefit from the conversati
 * You can add other [calendars](calendar.google.com) on the left using "Find a Time", to see when GitLab team members are free to schedule a meeting with. Please be cognizant of people time zones.
 * Use for example a tool like [Skyscanner](https://www.skyscanner.com) to find different flight options with most airlines when needing to book travel
 * Schedule calls in European timezones in the morning (am) Pacific (Daylight) Time and US time zones in the afternoon (pm) Pacific (Daylight) Time
-* Holds on the schedule should be removed at least 60 minutes before the preceeding meeting starts.
+* Holds on the schedule should be removed at least 60 minutes before the preceding meeting starts.
 * Meetings should be scheduled for 25 minutes or 50 minutes.  As a general guideline meetings should not be scheduled to the full 30/60 minute mark.
 * Monthly video calls are 25 minutes while quarterly calls/dinners are scheduled for 90 minutes plus any necessary travel time.
 * If the call is with any Google company, use Hangouts instead of Zoom.
@@ -139,7 +139,7 @@ If a flight was changed or not taken due to delays or other circumstances, make
 * Follow up on introductions from certain recipients (board, investors) immediately without asking for approval.
 * If Sid is meeting with a candidate, partner with recuriting to send the calendar invite through Greenhouse.
 * If Sid has a **ride or walks** to an appointment, make sure to **add 5 minutes extra** to find the address and sign in at reception.
-* If Sid is **driving himself**, make sure to **add 15 minutes extra** for random occurences such as traffic, stopping for gas or parking.
+* If Sid is **driving himself**, make sure to **add 15 minutes extra** for random occurrences such as traffic, stopping for gas or parking.
 * If Sid is **driving himself** to a meeting, he likes to plan phone calls to catch up with the team. Check with him who he'd like to talk with during his commute and schedule accordingly.
 * Due to a busy schedule Sid has a preference of meeting setup: First try for a video call or  a meeting in the GitLab boardroom. If the other party presses to meet at their location, confirm if that is OK before accepting.

source/handbook/engineering/compensation-roadmaps/template.html.md.erb

@@ -73,7 +73,7 @@ suppress_header: true
 ## Recommendation
-As of <b><%= compensation_roadmap.recommendation.date.strftime('%B %e, %Y') %></b> we beleive we should advocate for the following:
+As of <b><%= compensation_roadmap.recommendation.date.strftime('%B %e, %Y') %></b> we believe we should advocate for the following:
 <ul>
 <% compensation_roadmap.recommendation.recommendations.each do |recommendation| %>
   <li><%= recommendation %></li>

source/handbook/engineering/development/enablement/distribution/index.html.md.erb

@@ -229,7 +229,7 @@ don't hesitate to ping us in your issue and we'll gladly help.
 ## Engaging Distribution for expertise in support
-There are ocasions where the experise of the Distribution team may be needed in
+There are occasions where the experise of the Distribution team may be needed in
 support of a customer issue. When this does occur, the appropriate method of requesting
 our engagement is by opening an issue on the [Distribution team tracker][issue tracker]
 using the `Support Request` template. This process allows us to track time involved