@powerhousedao/academy 5.0.0-staging.9 → 5.0.1-staging.2

package/docs/academy/02-MasteryTrack/04-WorkWithData/06-Analytics Engine/graphql/integration.md

@@ -11,11 +11,17 @@ The `analytics-engine-graphql` module provides types and resolvers needed for a
 The graphql package contains typical resolvers and typedefs. The resolvers, however, are dependent on another object: `AnalyticsModel`. This object is responsible for connecting GQL types with an `IAnalyticsStore` implementation.
 
 ```typescript
-import { AnalyticsModel, AnalyticsResolvers, typedefs } from "@powerhousedao/analytics-engine-graphql";
+import {
+  AnalyticsModel,
+  AnalyticsResolvers,
+  typedefs,
+} from "@powerhousedao/analytics-engine-graphql";
 import { AnalyticsQueryEngine } from "@powerhousedao/analytics-engine-core";
 import { MemoryAnalyticsStore } from "@powerhousedao/analytics-engine-browser";
 
-const model = new AnalyticsModel(new AnalyticsQueryEngine(new MemoryAnalyticsStore()));
+const model = new AnalyticsModel(
+  new AnalyticsQueryEngine(new MemoryAnalyticsStore()),
+);
 ```
 
 > Note that the analytics resolvers require the passed in context to have an `AnalyticsModel` implementation on it. See below for details.
@@ -30,10 +36,14 @@ import http from "http";
 
 import { makeExecutableSchema } from "@graphql-tools/schema";
 import { ApolloServer } from "@apollo/server";
-import { expressMiddleware } from '@apollo/server/express4';
-import { ApolloServerPluginDrainHttpServer } from '@apollo/server/plugin/drainHttpServer';
-
-import { AnalyticsModel, AnalyticsResolvers, typedefs } from "@powerhousedao/analytics-engine-graphql";
+import { expressMiddleware } from "@apollo/server/express4";
+import { ApolloServerPluginDrainHttpServer } from "@apollo/server/plugin/drainHttpServer";
+
+import {
+  AnalyticsModel,
+  AnalyticsResolvers,
+  typedefs,
+} from "@powerhousedao/analytics-engine-graphql";
 import { AnalyticsQueryEngine } from "@powerhousedao/analytics-engine-core";
 import { MemoryAnalyticsStore } from "@powerhousedao/analytics-engine-browser";
 
@@ -48,7 +58,10 @@ const schema = makeExecutableSchema({
 });
 
 // create an apollo instance
-const plugins = [ApolloServerPluginDrainHttpServer({ httpServer }), responseCachePlugin()];
+const plugins = [
+  ApolloServerPluginDrainHttpServer({ httpServer }),
+  responseCachePlugin(),
+];
 const server = new ApolloServer({
   schema,
   plugins,
@@ -57,9 +70,12 @@ const server = new ApolloServer({
 await server.start();
 
 // needed by the analytics resolvers
-const model = new AnalyticsModel(new AnalyticsQueryEngine(new MemoryAnalyticsStore()));
+const model = new AnalyticsModel(
+  new AnalyticsQueryEngine(new MemoryAnalyticsStore()),
+);
 
-app.use("/graphql",
+app.use(
+  "/graphql",
   express.json(),
   expressMiddleware(server, {
     context: ({ req }) => {

package/docs/academy/02-MasteryTrack/04-WorkWithData/06-Analytics Engine/intro.md

@@ -109,7 +109,7 @@ The analytics engine supports various granularity options, each suitable for dif
 5. `monthly` : Monthly granularity is useful for a more detailed view of trends and patterns, particularly useful for operational planning and monitoring.
 
 6. `weekly` : Provides weekly data aggregation, which is helpful for short-term performance tracking and operational adjustments.
-daily: Offers a day-to-day breakdown, ideal for detailed analysis of daily operations or events.
+   daily: Offers a day-to-day breakdown, ideal for detailed analysis of daily operations or events.
 
 7. `hourly`: The most granular level, providing insights into hourly fluctuations. Useful in scenarios where short-term data spikes or dips are significant.
 
@@ -118,7 +118,7 @@ daily: Offers a day-to-day breakdown, ideal for detailed analysis of daily opera
 - Data Volume: Higher granularity (like hourly or daily) results in a larger volume of data points, providing more detailed insights but potentially leading to more complex analysis. Lower granularity (like annual or total) simplifies the data into fewer, broader data points.
 
 - Trend Analysis: Finer granularity helps in identifying short-term trends and anomalies, whereas coarser granularity is better for long-term trend analysis and strategic planning.
-Performance Impact: Queries with finer granularity might be more resource-intensive and take longer to execute due to the larger number of data points processed.
+  Performance Impact: Queries with finer granularity might be more resource-intensive and take longer to execute due to the larger number of data points processed.
 
 - Contextual Relevance: The choice of granularity should match the context of the analysis. For instance, financial planning might prefer annual or quarterly granularity, while operational monitoring might require daily or hourly data.
 
@@ -130,20 +130,20 @@ In summary, the choice of granularity in your query significantly influences the
 
 These are high-level definitions of major terms you will need to know.
 
-* **AnalyticsSeries** - The individual metric values, comprised of `(value, start, end)`. There should be one of these for every change in value.
+- **AnalyticsSeries** - The individual metric values, comprised of `(value, start, end)`. There should be one of these for every change in value.
 
-* **AnalyticsDimension** - Shared objects that decorate series objects with `name` and `path` information. Used to relate metrics to one another.
+- **AnalyticsDimension** - Shared objects that decorate series objects with `name` and `path` information. Used to relate metrics to one another.
 
-* **Path** - Composable, `/`-delimited string field on dimension that is used to _determine specificity_ during queries.
+- **Path** - Composable, `/`-delimited string field on dimension that is used to _determine specificity_ during queries.
 
-* **LOD** - A number that, when paired with `path`, determines how to aggregate values across dimensions.
+- **LOD** - A number that, when paired with `path`, determines how to aggregate values across dimensions.
 
-* **Granularity** - Determines how to aggregate values over time, like "monthly" or "yearly".
+- **Granularity** - Determines how to aggregate values over time, like "monthly" or "yearly".
 
 ## Next steps
 
 Next steps depend on use case.
 
-* For developers looking to **input data**, or **query data with Typescript**, see the [Typescript](./typescript/) docs.
-* For developers interested in **querying data with GraphQL**, see the [GraphQL](./graphql/) documentation. Data cannot be input through GraphQL.
-* For developers interested in **contributing to this project**, see the developer documentation [on GitHub](https://github.com/powerhouse-inc/analytics-engine).
+- For developers looking to **input data**, or **query data with Typescript**, see the [Typescript](./typescript/) docs.
+- For developers interested in **querying data with GraphQL**, see the [GraphQL](./graphql/) documentation. Data cannot be input through GraphQL.
+- For developers interested in **contributing to this project**, see the developer documentation [on GitHub](https://github.com/powerhouse-inc/analytics-engine).

package/docs/academy/02-MasteryTrack/04-WorkWithData/06-Analytics Engine/typescript/benchmarks.md

@@ -24,4 +24,4 @@ In [this benchmark](https://github.com/powerhouse-inc/analytics-engine/blob/main
 | ------------ | ----------- | ------------ |
 | Init         | 3           | 323.00 ms    |
 | 100 Inserts  | 478         | 2.08 ms      |
-| 200k Inserts | 0           | 4448.10 ms   |
+| 200k Inserts | 0           | 4448.10 ms   |

package/docs/academy/02-MasteryTrack/04-WorkWithData/06-Analytics Engine/typescript/index.md

@@ -70,7 +70,9 @@ const results = await engine.execute({
   currency: AnalyticsPath.fromArray(["DAI"]),
   metrics: ["Forecast"],
   select: {
-    report: [AnalyticsPath.fromArray(["atlas", "EcosystemActor", "50", "2023", "11"])],
+    report: [
+      AnalyticsPath.fromArray(["atlas", "EcosystemActor", "50", "2023", "11"]),
+    ],
   },
   granularity: 0,
   lod: {},
@@ -111,11 +113,11 @@ type GroupedPeriodResult = {
 - `unit`: This indicates the unit of measurement for the metric, such as quantities, currency (e.g., `"DAI"`), or percentages.
 
 - `dimensions`: A nested array that provides context for the metric by breaking it down into finer categories or segments, such as `"project"` or `"category"`. Each dimension can contain:
-    - `name`: The identifier or key for the dimension.
-    - `path`: A structured representation of the dimension's hierarchy or location within a dataset.
-    - `label`: A human-readable label for the dimension, which can be used for display purposes.
-    - `description`: A brief explanation of the dimension to give users an understanding of what it represents.
-    - `icon`: A graphical representation or icon associated with the dimension for easier identification in user interfaces.
+  - `name`: The identifier or key for the dimension.
+  - `path`: A structured representation of the dimension's hierarchy or location within a dataset.
+  - `label`: A human-readable label for the dimension, which can be used for display purposes.
+  - `description`: A brief explanation of the dimension to give users an understanding of what it represents.
+  - `icon`: A graphical representation or icon associated with the dimension for easier identification in user interfaces.
 
 - `value`: The actual numerical value of the metric for each row within the specified period.
 
@@ -160,7 +162,7 @@ await store.addSeriesValue([
     dimensions: {
       budget: AnalyticsPath.fromString("atlas/legacy/core-units/PE-001"),
       category: AnalyticsPath.fromString(
-        "atlas/headcount/CompensationAndBenefits/FrontEndEngineering"
+        "atlas/headcount/CompensationAndBenefits/FrontEndEngineering",
       ),
       project: source,
     },
@@ -176,11 +178,14 @@ The `IAnalyticsStore` also provides an API for subscribing to data changes. This
 const store = new MemoryAnalyticsStore();
 
 // subscribe
-const unsub = store.subscribeToSource(AnalyticsPath.fromString("atlas/"), (source) => {
-  console.log('Atlas data was changed!');
+const unsub = store.subscribeToSource(
+  AnalyticsPath.fromString("atlas/"),
+  (source) => {
+    console.log("Atlas data was changed!");
 
-  // decide whether or not to requery
-});
+    // decide whether or not to requery
+  },
+);
 
 // elided
 

package/docs/academy/02-MasteryTrack/04-WorkWithData/06-Analytics Engine/typescript/memory.md

@@ -40,15 +40,16 @@ const knex = knexFactory({ client: "pg", useNullAsDefault: true });
 
 // create your own Pglite instance and pass it in
 // See (https://github.com/electric-sql/pglite/blob/main/packages/pglite/src/interface.ts) for full list of options.
-const pgLiteFactory = () => PGlite.create({
-  debug: 3,
-  relaxedDurability: false,
-});
+const pgLiteFactory = () =>
+  PGlite.create({
+    debug: 3,
+    relaxedDurability: false,
+  });
 
 const store = new MemoryAnalyticsStore({
   knex,
   pgLiteFactory,
-})
+});
 ```
 
 ## Initialization

package/docs/academy/02-MasteryTrack/04-WorkWithData/06-Analytics Engine/typescript/schema.md

@@ -1,9 +1,9 @@
 # Database schema
 
 ![untitled](../images/dbs.png)
-*Database table structures for the analytics engine.*
+_Database table structures for the analytics engine._
 
-Analytics information  is stored in three database tables: 
+Analytics information is stored in three database tables:
 
 - `AnalyticsSeries`: This table stores the raw data over a period with its metric, value, unit, function and parameters.
 - `AnalyticsDimension`: This table stores all available dimensions for each series.

package/docs/academy/02-MasteryTrack/04-WorkWithData/06-Analytics Engine/typescript/utilities.md

@@ -48,7 +48,9 @@ The `AnalyticsProfiler` requires a namespace and a logger.
 ```typescript
 const profiler = new AnalyticsProfiler(
   "my-system",
-  (metricName: string, ms: number) => console.log(`[${metricName}] ${Math.floor(ms)} ms`));
+  (metricName: string, ms: number) =>
+    console.log(`[${metricName}] ${Math.floor(ms)} ms`),
+);
 ```
 
 > This object may be passed in through the constructor.
@@ -86,17 +88,17 @@ Often, it is useful to group metrics together. This is accomplished through a me
 // Blocks, { }, are a good convention to signal stack depth.
 profiler.push("system");
 {
-  profiler.recordSync("a", myFuncA);    // my-system.system.a
+  profiler.recordSync("a", myFuncA); // my-system.system.a
 
   profiler.push("subsystem");
   {
-    profiler.recordSync("b", myFuncB);  // my-system.system.subsystem.b
+    profiler.recordSync("b", myFuncB); // my-system.system.subsystem.b
   }
   profiler.pop();
 
-  profiler.recordSync("c", myFuncC);    // my-system.system.c
+  profiler.recordSync("c", myFuncC); // my-system.system.c
 }
 profiler.pop();
 
-profiler.recordSync("d", myFuncC);      // my-system.c
+profiler.recordSync("d", myFuncC); // my-system.c
 ```

package/docs/academy/02-MasteryTrack/04-WorkWithData/06-Analytics Engine/use-cases/maker.md

@@ -47,43 +47,34 @@ The above query will output the following list, which is described in the dropdo
 <summary>👉 Expand this dropdown to explore the list of fields and retrievable data.</summary>
 
 - **Actuals**: This metric represents the recorded amounts that have been actually spent or received. It is used for tracking and comparing against budgeted or forecasted amounts. This will be helpful to understand the real financial performance.
-
-    - Example Use Case: Comparing actual spending against the budget for a specific project to assess financial management efficiency.
+  - Example Use Case: Comparing actual spending against the budget for a specific project to assess financial management efficiency.
 
 - **Budget**: The estimated financial plan for a period, detailing the expected amounts allocated for various expenses and revenues.
-    - Example Use Case: Planning financial allocations for upcoming quarters and tracking the distribution of funds across different departments.
+  - Example Use Case: Planning financial allocations for upcoming quarters and tracking the distribution of funds across different departments.
 
 - **Forecast**: A projection of future financial outcomes based on current trends and past data. This functions as an educated estimate that helps in planning and strategy.
-
-    - Example Use Case: Anticipating cash flow and financial needs for the next fiscal year to make informed business decisions and adjustments.
+  - Example Use Case: Anticipating cash flow and financial needs for the next fiscal year to make informed business decisions and adjustments.
 
 - **PaymentsOnChain**: This metric tracks transactions executed on the blockchain, ensuring transparency and immutability of payment records.
-
-    - Example Use Case: Auditing blockchain transactions to ensure the accuracy of financial reporting within decentralized finance operations.
+  - Example Use Case: Auditing blockchain transactions to ensure the accuracy of financial reporting within decentralized finance operations.
 
 - **PaymentsOffChainIncluded**: Reflects transactions that occur outside the blockchain but are recognized in the financial records, possibly including traditional banking transactions and off-chain payment channels.
-
-    - Example Use Case: Reconciling on-chain and off-chain financial activities to maintain a comprehensive understanding of total expenditures and revenues.
+  - Example Use Case: Reconciling on-chain and off-chain financial activities to maintain a comprehensive understanding of total expenditures and revenues.
 
 - **DailyDaiPriceChange**: This metric measures the daily fluctuation in the price of DAI in USD. It's crucial for understanding the stability of DAI and its performance against the US dollar on a day-to-day basis.
-
-    - Example Use Case: Monitoring the stability of DAI to ensure it maintains its peg to the US dollar, crucial for financial planning and risk assessment in DAI-denominated transactions.
+  - Example Use Case: Monitoring the stability of DAI to ensure it maintains its peg to the US dollar, crucial for financial planning and risk assessment in DAI-denominated transactions.
 
 - **DailyUsdcPriceChange**: Tracks the daily price change of USDC in USD. This metric is important for analyzing USDC's stability and its daily performance relative to the US dollar.
-
-    - Example Use Case: Evaluating the daily fluctuations of USDC to assess its reliability as a stablecoin for operational liquidity and treasury management.
+  - Example Use Case: Evaluating the daily fluctuations of USDC to assess its reliability as a stablecoin for operational liquidity and treasury management.
 
 - **DailyUsdpPriceChange**: Reflects the daily price movement of USDP (Pax Dollar) in USD. It provides insights into the daily stability and performance of USDP against the US dollar.
-
-    - Example Use Case: Analyzing USDP's stability for strategic decisions in treasury operations, especially for entities holding or transacting in USDP.
+  - Example Use Case: Analyzing USDP's stability for strategic decisions in treasury operations, especially for entities holding or transacting in USDP.
 
 - **DailyMkrPriceChange**: This metric shows the daily variation in the price of MKR in USD. It is vital for stakeholders to track the governance token's market performance on a daily basis.
-
-    - Example Use Case: Investors and MKR holders use this data to make informed decisions regarding buying, selling, or holding MKR based on its daily market performance.
+  - Example Use Case: Investors and MKR holders use this data to make informed decisions regarding buying, selling, or holding MKR based on its daily market performance.
 
 - **DailyEthPriceChange**: Measures the daily price change of Ethereum (ETH) in USD. Given Ethereum's centrality to the DeFi ecosystem, this metric is key for evaluating the daily market dynamics of ETH.
-
-    - Example Use Case: DeFi participants and investors track ETH's price fluctuations to adjust their investment strategies, hedge risks, and capitalize on market movements.
+  - Example Use Case: DeFi participants and investors track ETH's price fluctuations to adjust their investment strategies, hedge risks, and capitalize on market movements.
 
 </details>
 
@@ -107,7 +98,7 @@ query Analytics {
 }
 ```
 
-The output of the query above: 
+The output of the query above:
 
 ```graphql
 {
@@ -201,42 +192,24 @@ The output of the query above:
 
 <summary> Expand this dropdown to explore the list of fields and retrievable data.</summary>
 
-**Budget**
-    - **Description**: Refers to the allocation and utilization of funds within different projects or operational areas. It includes various budget categories such as recognized delegates, specific projects, and governance facilitation.
+**Budget** - **Description**: Refers to the allocation and utilization of funds within different projects or operational areas. It includes various budget categories such as recognized delegates, specific projects, and governance facilitation.
 
 - **Values**:
-    - Paths like `atlas/legacy/recognized-delegates/` and `atlas/scopes/SUP/I/PHOENIX/` represent different budget categories or segments.
-    - Labels, descriptions, and icons are provided for more detailed budget segments, aiding in identifying specific budget areas and their purposes.
-
-**Category**
-    - **Description**: Categorizes transactions or allocations into broader groups like compensation, benefits, or non-headcount expenses.
-    - **Values**:
-        - Paths like `atlas/headcount/CompensationAndBenefits/` and `atlas/non-headcount/` help segregate financial data into meaningful categories for analysis.
-
-**Wallet**
-    - **Description**: Tracks transactions or balances associated with specific blockchain wallet addresses.
-    - **Values**:
-        - Each path, like `atlas/0xbe8e3e3618f7474f8cb1d074a26affef007e98fb/`, corresponds to a unique wallet address, enabling financial tracking at the wallet level.
-
-**Project**
-    - **Description**: Represents different projects or initiatives within the MakerDAO ecosystem.
-    - **Values**:
-        - Paths such as `atlas/Flip Flap Flop Delegate LLC/` and `atlas/Feedblack Loops LLC/` designate various projects, facilitating project-specific financial analysis and reporting.
-
-**Report**
-    - **Description**: Used for accessing specific financial reports, typically segmented by time (e.g., monthly, quarterly).
-    - **Values**:
-        - Paths like `atlas/Delegates/null/2021/11/` represent report segments, often organized by date, allowing users to access financial information for specific time periods.
-
-**TransactionType**
-    - **Description**: Differentiates between various types of transactions within the MakerDAO ecosystem. This dimension helps in analyzing transaction flows, such as internal transfers, governance actions, or external payments.
-    - **Values**:
-        - A path like `atlas/Internal Transaction/` signifies a specific category of transaction, in this case, internal transactions within the organization. This allows for a focused analysis of internal fund movements or operational transactions.
-
-**PriceData**
-    - **Description**: Provides access to historical price data for different cryptocurrencies, facilitating financial analysis and market trend observations. This dimension is crucial for tracking the day-to-day or historical price movements of tokens like MKR, DAI, etc.
-    - **Values**:
-        - Paths such as `atlas/price-data/mkr-usd/day-average/` offer access to daily average prices of MKR in USD, enabling detailed analysis of MKR's price performance over time. This can be invaluable for financial reporting, investment analysis, or economic research within the MakerDAO ecosystem.
+  - Paths like `atlas/legacy/recognized-delegates/` and `atlas/scopes/SUP/I/PHOENIX/` represent different budget categories or segments.
+  - Labels, descriptions, and icons are provided for more detailed budget segments, aiding in identifying specific budget areas and their purposes.
+
+**Category** - **Description**: Categorizes transactions or allocations into broader groups like compensation, benefits, or non-headcount expenses. - **Values**: - Paths like `atlas/headcount/CompensationAndBenefits/` and `atlas/non-headcount/` help segregate financial data into meaningful categories for analysis.
+
+**Wallet** - **Description**: Tracks transactions or balances associated with specific blockchain wallet addresses. - **Values**: - Each path, like `atlas/0xbe8e3e3618f7474f8cb1d074a26affef007e98fb/`, corresponds to a unique wallet address, enabling financial tracking at the wallet level.
+
+**Project** - **Description**: Represents different projects or initiatives within the MakerDAO ecosystem. - **Values**: - Paths such as `atlas/Flip Flap Flop Delegate LLC/` and `atlas/Feedblack Loops LLC/` designate various projects, facilitating project-specific financial analysis and reporting.
+
+**Report** - **Description**: Used for accessing specific financial reports, typically segmented by time (e.g., monthly, quarterly). - **Values**: - Paths like `atlas/Delegates/null/2021/11/` represent report segments, often organized by date, allowing users to access financial information for specific time periods.
+
+**TransactionType** - **Description**: Differentiates between various types of transactions within the MakerDAO ecosystem. This dimension helps in analyzing transaction flows, such as internal transfers, governance actions, or external payments. - **Values**: - A path like `atlas/Internal Transaction/` signifies a specific category of transaction, in this case, internal transactions within the organization. This allows for a focused analysis of internal fund movements or operational transactions.
+
+**PriceData** - **Description**: Provides access to historical price data for different cryptocurrencies, facilitating financial analysis and market trend observations. This dimension is crucial for tracking the day-to-day or historical price movements of tokens like MKR, DAI, etc. - **Values**: - Paths such as `atlas/price-data/mkr-usd/day-average/` offer access to daily average prices of MKR in USD, enabling detailed analysis of MKR's price performance over time. This can be invaluable for financial reporting, investment analysis, or economic research within the MakerDAO ecosystem.
+
 </details>
 
 ### Currency
@@ -267,7 +240,6 @@ query Analytics($filter: AnalyticsFilter) {
     }
   }
 }
-
 ```
 
 With filters for MKR:
@@ -284,6 +256,7 @@ With filters for MKR:
   }
 }
 ```
+
 This query will return budget data in MKR for the specified time frame and dimension.
 
 3. Consistency in Currency Specification: It's essential to be consistent in specifying the currency for each query. If your analysis involves comparing data across both DAI and MKR, ensure that separate queries are made for each currency and the results are appropriately labeled and distinguished.
@@ -314,6 +287,7 @@ By appropriately specifying the currency in your queries, you can tailor the fin
   }
 }
 ```
+
 This configuration fetches total MKR budget data for the entire year of 2023, focusing on the 'budget' dimension with a specific level of detail.
 
 2. Comprehensive Yearly Financial Analysis in DAI:
@@ -337,6 +311,7 @@ This configuration fetches total MKR budget data for the entire year of 2023, fo
 }
 
 ```
+
 This filter setup is designed to provide an annual overview of actuals and forecast data across all categories in DAI for the year 2023.
 
 These examples demonstrate how to construct a complete filter object for different types of financial analysis. By properly defining each parameter, users can ensure accurate and relevant data retrieval from the analytics engine.
@@ -353,7 +328,7 @@ The `multiCurrencySeries` is a new feature introduced to the MakerDAO Analytics
 
 The conversion is based on the available price change metrics in the analytics engine. To see all available price change metrics in the engine, use the metricsfield in the query to get a list:
 
-```graphql	
+```graphql
  "metrics": [
         "Actuals",
         "Budget",
@@ -530,7 +505,6 @@ query MyAnalyticsQuery($filter: AnalyticsFilter) {
     }
   }
 }
-
 ```
 
 **Step 6: Execute the Query**
@@ -598,7 +572,7 @@ Explanation
 
 - This query fetches the total actual expenses and budget for MakerDAO for the entire year of 2023.
 - The granularity is set to "total" to aggregate data across the whole year.
-metrics include "Actuals" and "Budget" to get both actual spendings and budgeted amounts.
+  metrics include "Actuals" and "Budget" to get both actual spendings and budgeted amounts.
 - The currency is set to "DAI" to ensure all financial data is in the DAI format.
 
 Modification for Custom Use Cases

package/docs/academy/02-MasteryTrack/04-WorkWithData/06-Analytics Engine/use-cases/processors.md

@@ -1,3 +1,3 @@
 # Processors
 
-See the Analytics Processor documentation for a thorough walkthrough of using the analytics system inside of a reactor processor to track metrics around document model operations.
+See the Analytics Processor documentation for a thorough walkthrough of using the analytics system inside of a reactor processor to track metrics around document model operations.