Skip to content

Commit

Permalink
Fix a bunch of typos
Browse files Browse the repository at this point in the history
  • Loading branch information
Zifius committed Feb 8, 2022
1 parent fe748bd commit 6509c93
Show file tree
Hide file tree
Showing 21 changed files with 60 additions and 60 deletions.
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Adobe Commerce Extensibility Strategy
description: Learn how Adobe Commerce's exttensibility model empowers you to customize your implementation.
description: Learn how Adobe Commerce's extensibility model empowers you to customize your implementation.
exl-id: fac4630d-8a41-40dc-899a-01eabceaa61e
---
# Extensibility strategy
Expand Down
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Adobe Commerce Global Reference Architecture
description: Get the most our of your Adobe Commerce implementaiton by leveraging a global reference architecture.
description: Get the most our of your Adobe Commerce implementation by leveraging a global reference architecture.
exl-id: a18529a3-da9b-4e1b-8048-0a906e65c740
---
# Global Reference Architecture (GRA)
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ exl-id: eac9d5b1-4917-4d2a-a8af-7f85c825fa0d
---
# Headless Adobe Commerce Architecture

The benefit of Adobe Commerce’s architecture is that it’s not an all-or-nothing proposition and a merchant can find the right mix of solutions for their business. They can build a PWA Studio-powered PWA for their primary site experience or use Adobe Experience Manaager as the layer in complex customer journeys, all while building out a custom frontend to experiment with new touchpoints. No other platform can match the time to market benefits and the flexibility that Adobe Commerce offers with its headless architecture.
The benefit of Adobe Commerce’s architecture is that it’s not an all-or-nothing proposition and a merchant can find the right mix of solutions for their business. They can build a PWA Studio-powered PWA for their primary site experience or use Adobe Experience Manager as the layer in complex customer journeys, all while building out a custom frontend to experiment with new touchpoints. No other platform can match the time to market benefits and the flexibility that Adobe Commerce offers with its headless architecture.

![Diagram showing a headless Adobe Commerce storefront architecture](../../../assets/playbooks/headless-storefront-architecture.svg)

Expand All @@ -25,17 +25,17 @@ The first is a progressive web application built with PWA Studio. Part of this i

Most merchants understand the direction that the industry is heading toward with regards to PWAs and many potential blockers are being removed rapidly.

Week over week, the number of partners building expertise in PWA Studio grows and we have an accelerating number of customer launches. The most recent update to PWA Studio included extensibility that will help make significant progress in compatibility with ADobe Commerce Marketplace extensions.
Week over week, the number of partners building expertise in PWA Studio grows and we have an accelerating number of customer launches. The most recent update to PWA Studio included extensibility that will help make significant progress in compatibility with Adobe Commerce Marketplace extensions.

Many merchants may feel they aren’t ready for headless and PWAs because they require heavy reliance on developers. One of the huge benefits of having both the commerce application and the head developed by Adobe Commerce is that it helps ensure compatibility across commerce capabilities.

In order to make PWAs more accessible and easier to manage for our merchants, we empower business users to manage day-to-day content changes, create new landing pages, and more using Page Builder. These two powerful capabilities together enable speed to market across all devices and experiences.

## Adobe Experience Manager

A powerhouse combination for your content and digital asset management needs,Adobe Exeprience Manager helps merchants get personalized, content-led experiences into market faster, combining digital asset management with the power of machine learning, Adobe Sensei-powered content, and customer journey management.
A powerhouse combination for your content and digital asset management needs, Adobe Experience Manager helps merchants get personalized, content-led experiences into market faster, combining digital asset management with the power of machine learning, Adobe Sensei-powered content, and customer journey management.

Adobe Commerce plus Adobe Exeprience Manager is a powerful story in that the commerce engine allows businesses to enable commerce though customer interfaces that are powered by Adobe Experience Manager.
Adobe Commerce plus Adobe Experience Manager is a powerful story in that the commerce engine allows businesses to enable commerce though customer interfaces that are powered by Adobe Experience Manager.

## Custom Heads

Expand Down
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
---
title: Journey to Headless
description: Review a timeline of Adobe Commerce's jouirney to support headless architectures.
description: Review a timeline of Adobe Commerce's journey to support headless architectures.
exl-id: 9286e6b3-3c29-4428-b353-f66eb4bc382d
---
# Adobe Commerce’s Journey to Headless

![Timeline of Adobe Commerce's hjourney to a headless architecture](../../../assets/playbooks/journey-to-headless.svg)
![Timeline of Adobe Commerce's journey to a headless architecture](../../../assets/playbooks/journey-to-headless.svg)
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Adobe Commerce Microservices
description: Be able to differentiate between healdess and microservices as it pertains to Adobe Commerce.
description: Be able to differentiate between headless and microservices as it pertains to Adobe Commerce.
exl-id: 078e0e8e-7acc-4913-8b78-585a950f3f5e
---
# Headless and microservices
Expand All @@ -9,7 +9,7 @@ It is important not to confuse headless with microservices. A lot of the time, w

A microservices architecture is a term used to describe the practice of breaking up an application into a collection of smaller, loosely coupled services. Microservices enable individual backend services to be:

- **Isolated from one another**—For exmaple, the pricing service has no dependency on the catalog service.
- **Isolated from one another**—For example, the pricing service has no dependency on the catalog service.

- **Deployed a la carte**—Customers deploy only the parts of the application that they need.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ The following diagram describes a monolithic approach that uses Adobe Commerce a

## Headless

The following diagram describes a headless approach that uses Adobe Commerce as the backend systenm integrated with a DXP/CMS/custom application as the storefront application:
The following diagram describes a headless approach that uses Adobe Commerce as the backend system integrated with a DXP/CMS/custom application as the storefront application:

![Adobe Commerce headless diagram](../../assets/playbooks/integration-headless.svg)

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ The ability to integrate your platform is “non-negotiable.” Companies want t

A holistic integration approach for both storefront and backend systems are supported by performant GraphQL APIs, comprehensive REST APIs, and batch-file import between Adobe Commerce and other systems or services.

The Adobe Commerce GraphQL API provides comprehesnive storefront coverage that you can use to integrate with other storefronts, including:
The Adobe Commerce GraphQL API provides comprehensive storefront coverage that you can use to integrate with other storefronts, including:

- Digital experience platforms (DXPs) like Adobe Exeprience Manaber and Bloomreach
- Content management systems (CMS) like Drupal and WordPress
Expand Down
2 changes: 1 addition & 1 deletion help/implementation-playbook/development/platform-tools.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ The following table includes solutions that we recommend and can be used within
| Message queue services | RabbitMQ |
| Security scan tool | SonarQube, ZAP |

## Datbase
## Database

There are three different tools that we use depending on the needs of the brand. MySQL is a great baseline solution as the Adobe Commerce database if you don’t expect your store to handle extreme loads.

Expand Down
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
---
title: Managed Services
description: Review the responsibilities of Adobe Managed Services, customers, and cloud service providers for your Adobe Commerce on cloud infrastructure implementaiton.
description: Review the responsibilities of Adobe Managed Services, customers, and cloud service providers for your Adobe Commerce on cloud infrastructure implementation.
exl-id: b1442e31-06f4-4aa6-b24a-b6cda630d52f
---
# Managed services

Adobe Commerce on cloud infrastructure manged services are secure by default.
Adobe Commerce on cloud infrastructure managed services are secure by default.

![Diagram showing Adobe Commerce managed services](../../../assets/playbooks/managed-services.svg)

Expand All @@ -15,7 +15,7 @@ Adobe Commerce Pro plans rely on a shared responsibility security model. In this

![Diagram showing Adobe Commerce shared responsibility model](../../../assets/playbooks/shared-responsibility.svg)

### Adobe Manged Services responsibilities
### Adobe Managed Services responsibilities

Adobe Managed Services is responsible for the security and availability of the Adobe Commerce Pro cloud environment, the core Adobe Commerce Pro application code, and internal commerce systems. This includes, but is not limited to:

Expand Down
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Cloud Infrastructure Overview
description: Learn about Adobe Commerce on cloud infrastucture.
description: Learn about Adobe Commerce on cloud infrastructure.
exl-id: 94cf1505-0853-4e01-ba55-befc1117fbdb
---
# Overview
Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: Cloud Infrasrtructure Security
title: Cloud Infrastructure Security
description: Learn about how we keep Adobe Commerce on cloud infrastructure secure.
exl-id: cd5d1106-c8db-4b70-b1c7-12378d7d77a7
---
Expand Down
4 changes: 2 additions & 2 deletions help/implementation-playbook/infrastructure/on-premises.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: On-premises Infrastructure
description: Learn about Adobe Commerce on-premises infrastucture and third-party cloud services.
description: Learn about Adobe Commerce on-premises infrastructure and third-party cloud services.
exl-id: de1467be-acec-4a0d-8229-e7e87614bc55
---
# Adobe Commerce on-premises infrastructure
Expand Down Expand Up @@ -43,7 +43,7 @@ In addition to providing a supporting technology platform for the enablement of

## Cloud migration

The value proposition for migrating Adobe Commerce to AWS is further enhanced by the availability of several services that provide operational insight and agility. What we mean is operational insight into the platform from not only a technical perspective (for exmaple, requests per hour) but also a business operational perspective (for example, orders per hour), particularly when the two sets of data can be married. This provides a near-real-time look into campaign performance, platform operations costs, and a near infinite number of other indicators.
The value proposition for migrating Adobe Commerce to AWS is further enhanced by the availability of several services that provide operational insight and agility. What we mean is operational insight into the platform from not only a technical perspective (for example, requests per hour) but also a business operational perspective (for example, orders per hour), particularly when the two sets of data can be married. This provides a near-real-time look into campaign performance, platform operations costs, and a near infinite number of other indicators.

Adobe Commerce setup to AWS can replace specific application dependencies with fully managed alternatives available in the cloud. For example, rather than directly hosting a relational database on EC2 instances, the database for many applications can be easily replaced by Amazon Relational Database Service (AmazonRDS). The benefit to this strategy is that the operating responsibility of undifferentiated components can be offloaded to AWS without requiring significant changes to the core application.

Expand Down
2 changes: 1 addition & 1 deletion help/implementation-playbook/infrastructure/overview.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Infrastructure and Deployment Overview
description: Get an overview of what we've taught you about the Adobe Commerce soluion so far.
description: Get an overview of what we've taught you about the Adobe Commerce solution so far.
exl-id: 8767bb83-9175-4a54-8c5c-c6af0931917c
---
# Overview
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ DNS lookup is the process of finding which IP address that the domain name belon

### Content delivery network (CDN)

Use a CDN to optimize asset downloading performance. Adobe Commerce uses Fastly. If have an on-premises implementaiton of Adobe Commerce, you should also consider adding a CDN layer.
Use a CDN to optimize asset downloading performance. Adobe Commerce uses Fastly. If have an on-premises implementation of Adobe Commerce, you should also consider adding a CDN layer.

### Web latency

Expand Down Expand Up @@ -97,19 +97,19 @@ Performance testing before each production release is always recommend to get an

>[!NOTE]
>
> Adobe Commerce on cloud infrastrucrure already applies all of the above infrastructure and architecture optimizations, except for the DNS lookup because it's out of scope.
> Adobe Commerce on cloud infrastructure already applies all of the above infrastructure and architecture optimizations, except for the DNS lookup because it's out of scope.
### Search

Elasticsearch is required as of Adobe Commerce version 2.4, but it’s also a best practice to enable it for versions prior to 2.4.

## Operating models

Apart from the previoiusly mentioend common infrastructure optimization recommendations, there are also approaches to enhance the performance for specific business modes and scales. This document does not provide in-depth tuning instructions for all of them because each scenario is different, but we can provide a few high-level options for your reference.
Apart from the previously mentioned common infrastructure optimization recommendations, there are also approaches to enhance the performance for specific business modes and scales. This document does not provide in-depth tuning instructions for all of them because each scenario is different, but we can provide a few high-level options for your reference.

### Headless architecture

We have a seperate section dedicated to detailing what [headless](../../architecture/headless/adobe-commerce.md) is and different options. In summary, it separates the storefront layer from the platform itself. It is still the same backend, but Adobe Commerce no longer processes requests directly and instead only supports custom storefronts through the GraphQL API.
We have a separate section dedicated to detailing what [headless](../../architecture/headless/adobe-commerce.md) is and different options. In summary, it separates the storefront layer from the platform itself. It is still the same backend, but Adobe Commerce no longer processes requests directly and instead only supports custom storefronts through the GraphQL API.

### Keep Adobe Commerce updated

Expand Down
6 changes: 3 additions & 3 deletions help/implementation-playbook/intro/platform-development.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,14 +18,14 @@ In this playbook, we dive deeper into some of the main standards of Adobe Commer

While some solution implementers may have their own preferences when it comes to the methodologies, processes, and tools used throughout an implementation project, this playbook focuses on generally accepted best practices and methodologies that can be shared across the majority of implementations.

Like any large IT project, Adobe Commerce is built on coding standards that leverage best practices and standardizations of the underlying technologies (for example, PHP/Zend,Symfony, JavaScript, jQuery, and HTML), as well as standards that have been established within the Adobe Commerce Coding Standard. Following these standards is an absolute must to eliminate bugs and improve the quality and maintainability of custom-built code.
Like any large IT project, Adobe Commerce is built on coding standards that leverage best practices and standardizations of the underlying technologies (for example, PHP/Zend, Symfony, JavaScript, jQuery, and HTML), as well as standards that have been established within the Adobe Commerce Coding Standard. Following these standards is an absolute must to eliminate bugs and improve the quality and maintainability of custom-built code.

## Adobe Commerce on cloud infrastructure

Adobe Commerce on cloud infrastructure is a managed, automated hosting platform for the Adobe Commerce software. Adobe Commerce on cloud infrastructure comes with a variety of additional features that sets it apart from on-premises Adobe Commerce and Magento Open Source implementations:

![Adobe Commerce component infgraphics](../../assets/playbooks/commerce-cloud.svg)
![Adobe Commerce component infographics](../../assets/playbooks/commerce-cloud.svg)

Adobe Commerce on cloud infrastructure provides a pre-provisioned infrastructure that includes PHP, MySQL, Redis, RabbitMQ, and Elasticsearch technologies; a Git-based workflow with automatic build and deploy operations for efficient rapid development and continuous deployment every time code changes are pushed in a Platform as a Service (PaaS) environment; highly customizable environment-configuration files and tools; and AWS hosting that offers a scalable and secure environment for online sales and retailing.

![Adobe Commerce component infgraphics](../../assets/playbooks/cloud-tech-stack.svg)
![Adobe Commerce component infographics](../../assets/playbooks/cloud-tech-stack.svg)
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Adobe Managed Services
description: Learn how ADobe Managed Services can help support and maintain your Adobe Commerce implementation.
description: Learn how Adobe Managed Services can help support and maintain your Adobe Commerce implementation.
exl-id: b600b0e3-c6fd-4b86-ad2a-a445e599f1bd
---
# Adobe Managed Services
Expand All @@ -21,4 +21,4 @@ Platform partners such as Amazon Web Services and Microsoft Azure ensures maximu

The following diagram shows Adobe Managed Service's security technology stack:

![Diagram showing ADobe Managed Services security stack](../../assets/playbooks/managed-services-security-stack.svg)
![Diagram showing Adobe Managed Services security stack](../../assets/playbooks/managed-services-security-stack.svg)
2 changes: 1 addition & 1 deletion help/implementation-playbook/maintenance/models.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Maintenance and Support Models
description: Use these common maintenance and support models to keep your ADobe Commerce implementation running smoothly.
description: Use these common maintenance and support models to keep your Adobe Commerce implementation running smoothly.
exl-id: 44469b83-a10b-44c2-8721-9a7daa2733d3
---
# Maintenance and support models
Expand Down
2 changes: 1 addition & 1 deletion help/implementation-playbook/planning/ownership.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Responsibility and Ownership
description: Define project roles and responsibilities to ensure a succesful Adobe Commerce implementation.
description: Define project roles and responsibilities to ensure a successful Adobe Commerce implementation.
exl-id: 206b6e3b-6dee-442e-a2ba-7867b2494b75
---
# Responsibility and ownership
Expand Down
2 changes: 1 addition & 1 deletion help/implementation-playbook/project-scope/knowledge.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Knowledge is Power
description: Learn why it's so important that everyone in your organizationinvests in your Adobe Commerce implementation.
description: Learn why it's so important that everyone in your organization invests in your Adobe Commerce implementation.
exl-id: a3929586-5ad2-4b30-8bc4-84da8f8b9eb5
---
# Knowledge is power
Expand Down
Loading

0 comments on commit 6509c93

Please sign in to comment.