docs(PrinciplesAndArchitectureOverview): fix typos/grammar
Summary: Pull Request resolved:
@@ -3,7 +3,7 @@ id: architecture-overview
title: Architecture Overview
---
-This document together [Runtime Architecture](runtime-architecture.html) and [Compiler Architecture](compiler-architecture.html) describe the high-level architecture of Relay "Modern". The intended audience includes developers interested in contributing to Relay, developers hoping to utilize the building blocks of Relay to create higher-level APIs, and anyone interested in understanding more about Relay internals. For developers wanting to learn more about *using* Relay to build products, the other sections might be more helpful.
+This document, together with [Runtime Architecture](runtime-architecture.html) and [Compiler Architecture](compiler-architecture.html), describes the high-level architecture of Relay "Modern". The intended audience includes developers interested in contributing to Relay, developers hoping to utilize the building blocks of Relay to create higher-level APIs, and anyone interested in understanding more about Relay internals. For developers wanting to learn more about *using* Relay to build products, the other sections might be more helpful.
## Core Modules
@@ -13,4 +13,4 @@ Relay Modern is composed of three core modules:
* **Relay Runtime:** A full-featured, high-performance GraphQL *runtime* that can be used to build higher-level client APIs. The runtime features a normalized object cache, optimized "write" and "read" operations, a generic abstraction for incrementally fetching field data (such as for pagination), garbage collection for removing unreferenced cache entries, optimistic mutations with arbitrary logic, support for building subscriptions and live queries, and more.
* **React/Relay:** A high-level *product API* that integrates the Relay Runtime with React. This is the primary public interface to Relay for most product developers, featuring APIs to fetch the data for a query or define data dependencies for reusable components (aka containers).
-Note that these modules are *loosely coupled*. For example, the compiler emits representations of queries in a well-defined format that the runtime consumes (the "Concrete" node interfaces in `RelayConcreteNode`), such that the compiler implementation could be swapped out if desired. React/Relay relies only on the well-documented public interface of the runtime, such that the actual implementation can be swapped out (in fact we've upgraded the classic Relay core to also implement this same API). We hope that this loose coupling will allow the community to explore new use-cases such as the development of specialized product APIs using the Relay runtime or integrations of the runtime with view libraries other than React.
+Note that these modules are *loosely coupled*. For example, the compiler emits representations of queries in a well-defined format that the runtime consumes (the "Concrete" node interfaces in `RelayConcreteNode`), such that the compiler implementation can be swapped out if desired. React/Relay relies only on the well-documented public interface of the runtime, such that the actual implementation can be swapped out (in fact, we've upgraded the classic Relay core to also implement this same API). We hope that this loose coupling will allow the community to explore new use-cases such as the development of specialized product APIs using the Relay runtime or integrations of the runtime with view libraries other than React.
