Skip to content

Commit

Permalink
Alright
Browse files Browse the repository at this point in the history
  • Loading branch information
zbuster05 authored Jun 23, 2021
1 parent 8448a12 commit 33583fa
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions src/CondutionEngine.ts
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ import CustomJSONProvider from "./Storage/Backends/CustomJSONBackend";
*
* With ReferenceManager's API, you get to control every data entry of Providers
* except, of course, if you got blocked server-side. This also means that you
* could delete whole users (if you have perms) and mess up the DB. So have fun!
* can delete whole users (if you have perms) and mess up the DB. So have fun!
*
* To use ReferenceManagers, instantiate with instances of the Providers that you
* want to setup. Then, call .use on the name on the provider's name that you want
Expand All @@ -100,9 +100,9 @@ import ReferenceManager from "./Storage/ReferenceManager";
/*
* Chapter 3: The Context
*
* This is THE most important piece of thing that may be confusing. Contexts are
* This is THE most important confusing bit in this backend. Contexts are
* a layer above managers that allow you to actually query for specific pages by
* users, manage workspaces, and get data using a similar syntax as does Managers
* users, and manage workspaces, all while using a similar syntax to that of Managers
* but without the confusing confusal of needing the know the UID, worry about workspaces
* etc.
*
Expand All @@ -120,7 +120,7 @@ import { Context } from "./Objects/EngineManager";
/*
* Chapter 4: The Objects
*
* Here are all the objects that Condution could manage for you! Tasks, Tags, Projects
* Here are all the objects that Condution can manage for you! Tasks, Tags, Projects
* all the rage! Unfortunately I am too swollen to type up docs at the moment, so
* TODO and just look in the inline documentation for yourself
*
Expand Down

0 comments on commit 33583fa

Please sign in to comment.