Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Corrected typos in documentation files #232

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/adr/000-adr-template.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@
## Context and Problem Statement

Describe the context and problem statement, e.g., in free form using two to three sentences or in the form of an illustrative story.
You may want to articulate the problem in form of a question and add links to collaboration boards or issue management systems.}
You may want to articulate the problem in form of a question and add links to collaboration boards or issue management systems.

## Considered Options

Expand Down
2 changes: 1 addition & 1 deletion docs/adr/002-ways-of-working.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ We agree to use these ways of working.

#### Merge commits

The merging process in all modern software projects can turn into a never-ending debate over whether to use merge commits, sqush, or rebase strategies. Our approach is to use the strategy that requires the least care before merging into main, which is the merge commit. Yes, the git blame and logs can get messy, but from our point of view it generates the least friction and potential rebasing problems.
The merging process in all modern software projects can turn into a never-ending debate over whether to use merge commits, squash, or rebase strategies. Our approach is to use the strategy that requires the least care before merging into main, which is the merge commit. Yes, the git blame and logs can get messy, but from our point of view it generates the least friction and potential rebasing problems.

#### Code delivery stages

Expand Down
2 changes: 1 addition & 1 deletion packages/mina-core/README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# @palladxyz/mina-core

@palladxyz/mina-core is a TypeScript package designed for helping other libraries to interact with Mina. It provides interfaces & types for many the main data strcutures of Mina that are relevant for wallets and applications. This includes providers that retrieve account information, process transaction history, submit transactions, and fetch health checks.
@palladxyz/mina-core is a TypeScript package designed for helping other libraries to interact with Mina. It provides interfaces & types for many the main data structures of Mina that are relevant for wallets and applications. This includes providers that retrieve account information, process transaction history, submit transactions, and fetch health checks.

## Installation

Expand Down