Skip to content

Commit

Permalink
[WIP] docs: fix typos (#455)
Browse files Browse the repository at this point in the history
  • Loading branch information
talal authored Sep 22, 2024
1 parent b7f7f49 commit 826c109
Show file tree
Hide file tree
Showing 8 changed files with 11 additions and 11 deletions.
4 changes: 2 additions & 2 deletions docs/advanced/bank-sync.md
Original file line number Diff line number Diff line change
Expand Up @@ -82,7 +82,7 @@ Here are a couple of considerations to know about before making the decision to

2. Select the Link your bank account button

![Add acount dialog](/static/img/connecting-your-bank/connecting-your-bank-03.png)
![Add account dialog](/static/img/connecting-your-bank/connecting-your-bank-03.png)

3. Select your country and bank from the list and click the Link bank in browser button

Expand All @@ -106,7 +106,7 @@ Here are a couple of considerations to know about before making the decision to

8. Once the connection has been made, there will be a list of your accounts that you can choose from

![Select bank acount you want to link](/static/img/connecting-your-bank/connecting-your-bank-09.png)
![Select bank account you want to link](/static/img/connecting-your-bank/connecting-your-bank-09.png)

9. The final step is to select the account you want to sync and click Link account

Expand Down
2 changes: 1 addition & 1 deletion docs/advanced/scripts/modify-transfers.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ This process will only apply when the below conditions are met

1. Create a second copy of the backup
2. Extract the backup
3. Open the `db.sqlite` file with your preferred tool [sqlite3 cli](https://www.sqlite.org/cli.html), [heidiSQL](https://www.heidisql.com/), ect
3. Open the `db.sqlite` file with your preferred tool [sqlite3 cli](https://www.sqlite.org/cli.html), [heidiSQL](https://www.heidisql.com/), etc.
4. Run the below query to first view the impacted transactions

```sql
Expand Down
6 changes: 3 additions & 3 deletions docs/budgeting/joint-accounts.md
Original file line number Diff line number Diff line change
Expand Up @@ -129,21 +129,21 @@ Situation: I am using Actual to keep track of my budget and finances, but I shar

Each month you will add a transfer of your share to the joint account from one of your on-budget accounts. You don't need a category for your contribution since it is just a transfer from one of your accounts to another.

![Screenshot of joint accounts in a personcal Acutal Budget file](/img/joint-accounts/jointaccount-2.png)
![Screenshot of joint accounts in a personal Actual Budget file](/img/joint-accounts/jointaccount-2.png)

#### Partner contribution

##### Option 1

When your partner makes a contribution to the joint account, use the **Income Category** you created as the category. By having a separate category for this contribution, it will be easier to filter out when doing reports later since this isn't true income, though it is income to the budget.

![Screenshot of joint accounts in a personal Acutal Budget file - option 1](/img/joint-accounts/jointaccount-3.png)
![Screenshot of joint accounts in a personal Actual Budget file - option 1](/img/joint-accounts/jointaccount-3.png)

##### Option 2

If option 1 doesn't seem right to you, the same result could be achieved by treating the new income like a return to a store. In this case, you can assign your partners deposit directly to the shared categories. The deposit should be made into the **Joint Account** ledger. As you can see, you can fund each shared category using the **split transaction** option.

![Screenshot of joint accounts in a personal Acutal Budget file - option 2](/img/joint-accounts/jointaccount-5.png)
![Screenshot of joint accounts in a personal Actual Budget file - option 2](/img/joint-accounts/jointaccount-5.png)

### Budgeting

Expand Down
2 changes: 1 addition & 1 deletion docs/budgeting/rules/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ When a transaction is imported, it runs against all of the rules **in the order

If there is a conflict, for example if two rules set the category, the rule that runs last will always win out.

Rules are **automatically ranked** from least to most specific. If the conditions of one rule apply broadly, while the conditions of another are more specific, the latter will always run _after_ the former so its changes always win out. This means you can make a broad rule like "if a transaction's payee _contains_ 'cat' set the category to 'pets'", and then fix a mis-matched transaction with another rule that says "if the payee _is_ 'catan' set the category to 'games'". An "is" condition always ranks higher than "contains". Generally, you don't need to worry about this and it should work like you expect.
Rules are **automatically ranked** from least to most specific. If the conditions of one rule apply broadly, while the conditions of another are more specific, the latter will always run _after_ the former so its changes always win out. This means you can make a broad rule like "if a transaction's payee _contains_ 'cat' set the category to 'pets'", and then fix a mismatched transaction with another rule that says "if the payee _is_ 'catan' set the category to 'games'". An "is" condition always ranks higher than "contains". Generally, you don't need to worry about this and it should work like you expect.

While ranking works for the most part, you might want to say "this rule _always_ should run last no matter what". Actual allows this with **stages**. Rules are actually run in 3 stages: `pre`, normal, and `post`. By tagging a rule as `pre` or `post`, you force it to always run before or after rules in the other stages. Within a stage, rules are still automatically ranked.

Expand Down
2 changes: 1 addition & 1 deletion docs/contributing/windows.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Building on Windows

Many of the build scripts are bash scripts and not natively invokable in Windows. To solve this, you can build the project using Git Bash.
Many of the build scripts are bash scripts and not natively invocable in Windows. To solve this, you can build the project using Git Bash.

1. Install [Git & Git Bash for Windows](https://git-scm.com/downloads)
2. Ensure you have activated [Developer Mode](https://docs.microsoft.com/en-us/windows/apps/get-started/enable-your-device-for-development)
Expand Down
2 changes: 1 addition & 1 deletion docs/getting-started/starting-fresh.md
Original file line number Diff line number Diff line change
Expand Up @@ -191,7 +191,7 @@ We can now see the budget numbers to be used for the month of August in the Aver

It's important to note that this method only works correctly if you use a debit or credit card for all your purchases.
As a result, your actual *start date* for your budget is in the past. We will reiterate our warning on
[how to set up acounts](#how-to-setup-accounts): going to far back, might make your budget completely
[how to set up accounts](#how-to-setup-accounts): going to far back, might make your budget completely
out of wack. It's crucial to avoid this, as you can easily spend more time trying to find out what's
wrong with your budget and spent numbers as "nothing adds up" anymore.

Expand Down
2 changes: 1 addition & 1 deletion docs/releases.md
Original file line number Diff line number Diff line change
Expand Up @@ -430,7 +430,7 @@ The release has the following notable improvements:
- [#2754](https://github.com/actualbudget/actual/pull/2754) Do not remember last entered category in mobile transaction entry. — thanks @joel-jeremy
- [#2765](https://github.com/actualbudget/actual/pull/2765) Do not use underlines for emphasis. — thanks @psybers
- [#2768](https://github.com/actualbudget/actual/pull/2768) Creating a callback for the table totals to fix a bug that created duplicate columns while rendering. — thanks @carkom
- [#2769](https://github.com/actualbudget/actual/pull/2769) Updating date range element to catch any incorrectly formated dates. Current state crashes app when dates are invalid. — thanks @carkom
- [#2769](https://github.com/actualbudget/actual/pull/2769) Updating date range element to catch any incorrectly formatted dates. Current state crashes app when dates are invalid. — thanks @carkom
- [#2773](https://github.com/actualbudget/actual/pull/2773) Fix notes icon changing size/position with long category or group names. — thanks @jpelgrom
- [#2774](https://github.com/actualbudget/actual/pull/2774) Move the rollover arrow into view. — thanks @Tigatok
- [#2775](https://github.com/actualbudget/actual/pull/2775) Adds income on left and expense on right always. Hide bar if value is 0. — thanks @Tigatok
Expand Down
2 changes: 1 addition & 1 deletion docs/tour/user-interface.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ The user interface is divided into three parts:
Standard on most screens:

* On the left, we have the sidebar, which lets you easily switch between the various views, such as Budget, Reports, and Accounts.
* The server and synch status (if used) are shown in the red box in the upper right corner.
* The server and sync status (if used) are shown in the red box in the upper right corner.
* The content of the rest of the interface depends on the functionality you have chosen in the sidebar. This screenshot shows an example of a Budget view.

![](/static/img/a-tour-of-actual/tour-overview-of-user-interface.png)
Expand Down

0 comments on commit 826c109

Please sign in to comment.