Merge pull request #3169 from FlowFuse/organization

Update references to from organisation to organization

Author: ZJvandeWeg

src/_data/pricingFeatures.yaml

@@ -51,7 +51,7 @@ sections:
         cloudValues: [ 'check', 'check', 'check', 'check' ]
         selfHostedValues: [ 'check', 'check' ]    
         tags: [ 'cloud', 'self-hosted' ]
-        info: "<p>Connect to edge devices to quickly assess and update logic. Debug one device and roll out improvements to your fleet in minutes. All securely without requiring full device access for your whole organisation.</p>"
+        info: "<p>Connect to edge devices to quickly assess and update logic. Debug one device and roll out improvements to your fleet in minutes. All securely without requiring full device access for your whole organization.</p>"
       - id: mqtt-broker-cloud
         label: MQTT Broker
         cloudValues: [ null, 'check', 'check', 'check' ]    

src/blog/2022/11/scaling-node-red-with-diy-tooling.md

@@ -70,7 +70,7 @@ devices. Scaling to that many devices and runtimes requires hours of development
 each week alongside monitoring, maintenance, and auditing.
 
 As a side effect of investing more time into Node-RED and its ecosystem the
-organisation has developed a few standards. Standard custom nodes that are
+organization has developed a few standards. Standard custom nodes that are
 pre-installed (👋 `moment.js`), a style guide published for developing flows,
 maybe even flow linting: https://github.com/node-red/nrlint
 

src/blog/2022/12/what-flowforge-adds-to-node-red.md

@@ -10,16 +10,16 @@ tags:
     - node-red
 ---
 
-Many organisations face challenges in IT/OT convergence. There are many protocols, disparate devices, and everything is a brownfield project. Furthermore, skilled engineers are hard to find. Many organisations find themselves maintaining systems and integrations, and have little time left to improve continuously.
+Many organizations face challenges in IT/OT convergence. There are many protocols, disparate devices, and everything is a brownfield project. Furthermore, skilled engineers are hard to find. Many organizations find themselves maintaining systems and integrations, and have little time left to improve continuously.
 
 <!--more-->
 
 This is why Node-RED is adopted so widely, it makes a world of difference through two of its properties: Low-Code Development and the ability to integrate with a wide range of hardware and software systems. Node-RED makes it easy to program data collection, then use that data for decision making, and provide feedback to both your digital platform and the physical reality of your business. Furthermore, Node-RED is unrivalled in making data accessible. The data previously locked in a walled garden of your hardware providers is now accessible and obtainable. With that, more data is available and better decisions are made, faster.
 
 FlowFuse makes developer collaboration, flow deployment, and scaling of infrastructure easy when working with Node-RED. It offers an intuitive user interface for creating, deploying, monitoring, and managing multiple Node-RED projects. FlowFuse also provides one-click deployment to thousands of devices, making it easy to manage large-scale environments. 
 
-These features make FlowFuse a valuable tool for organisations using Node-RED to build applications and automate processes. Enabling for further adoption of Node-RED to integrate more systems, for even better decisions.
+These features make FlowFuse a valuable tool for organizations using Node-RED to build applications and automate processes. Enabling for further adoption of Node-RED to integrate more systems, for even better decisions.
 
-This not only reduces operational costs but it also allows an organisation to be far more agile with their Node-RED projects than was possible without FlowFuse.
+This not only reduces operational costs but it also allows an organization to be far more agile with their Node-RED projects than was possible without FlowFuse.
 
 We would be happy to talk to you more about how FlowFuse can help you get the most value from Node-RED. Please [contact us](/contact-us/) to learn more.

src/blog/2023/02/highly-available-node-red.md

@@ -25,7 +25,7 @@ any software engineer. As a topic, it's studied when obtaining a Computer Scienc
 Bachelors degree, masters and even PhD. When tasked
 to make a HA system, it took me a good month to define what our goals
 were, and what we were willing to exchange for the properties sought. This
-might be extra hardware, engineering hours, as well as organisational challenges.
+might be extra hardware, engineering hours, as well as organizational challenges.
 For now, let's focus on the first two.
 
 Let's start with defining the goal; reduce the impact of a Node-RED instance

src/blog/2023/03/3-quick-node-red-tips-5.md

@@ -58,7 +58,7 @@ It's important to note that while custom node examples can be a useful starting
 
 The group feature in Node-RED allows users to visually group nodes together within the workspace. This feature offers several benefits:
 
-1. Improved organisation: The group feature allows you to group related nodes visually, which can make your flow easier to understand and navigate. This can be particularly helpful for larger, more complex flows.
+1. Improved organization: The group feature allows you to group related nodes visually, which can make your flow easier to understand and navigate. This can be particularly helpful for larger, more complex flows.
 
 2. Simplified editing: When you group nodes together, you can edit or move them as a single unit, rather than individually. This can save time and reduce the chance of errors.
 

src/blog/2024/05/node-red-mind-stack-with-flowfuse.md

@@ -7,7 +7,7 @@ tags:
     - changelog
 ---
 
-For organisations using Single Sign-On with FlowFuse, we have now added the ability
+For organizations using Single Sign-On with FlowFuse, we have now added the ability
 to manage their user's team memberships and roles via their Identity Provider.
 
 This makes it easier to control access to the FlowFuse Platform from providers such

src/changelog/2024/01/sso-team-membership.md

@@ -236,7 +236,7 @@ timeline if one was committed.
 
 ## Skip level meetings
 
-Meetings between levels of the organisation happen in regular 1:1s, usually held
+Meetings between levels of the organization happen in regular 1:1s, usually held
 weekly between the manager and report. The report however might want to
 also communicate with the manager's manager to keep in touch with the strategy and
 communicate feedback on what they observe directly.

src/handbook/company/communication.md

@@ -10,7 +10,7 @@ hubspot:
 ---
 
 <p>Below if the FlowFuse subscription agreement that applies to all self-hosted
-  installations. If you'd like to make alterations for your organisation, please
+  installations. If you'd like to make alterations for your organization, please
   download the .docx file in the following form and initiate the legal part of
   the negotiation through your account executive.</p>
 

src/handbook/customer/sales/subscription-agreement-1.5.njk

@@ -77,7 +77,7 @@ to match what is needed.
 #### Private Repositories
 
 For *private* repositories, you will also need to add a Repository Secret as
-they cannot access the organisation-wide secret we have in place.
+they cannot access the organization-wide secret we have in place.
 
 1. Generate a [Personal Access Token](https://github.com/settings/tokens) with
    `repo, write:org` scope.