Skip to content

Commit c91d9c9

Browse files
committed
Fix several links
1 parent 5141a17 commit c91d9c9

File tree

3 files changed

+9
-9
lines changed

3 files changed

+9
-9
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Get Ackee up and running…
2626

2727
And configure Ackee and your server correctly…
2828

29-
- […with environment variables](#options)
29+
- […with environment variables](docs/Options.md)
3030
- […with SSL and HTTPS enabled](docs/SSL%20and%20HTTPS.md)
3131
- […with CORS headers](docs/CORS%20headers.md)
3232

docs/CORS headers.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Access-Control-Allow-Origin: https://example.com
2929
Access-Control-Allow-Origin: *
3030
```
3131

32-
The `Access-Control-Allow-Origin` header only allows one domain or a wildcard (`*`). Take a look at our [advanced configuration](./SSL%20and%20HTTPS.md#advanced-configuration) if you want to allow requests from multiple domains without using the insecure wildcard.
32+
The `Access-Control-Allow-Origin` header only allows one domain or a wildcard (`*`). Take a look at our [advanced configuration](SSL%20and%20HTTPS.md#advanced-configuration) if you want to allow requests from multiple domains without using the insecure wildcard.
3333

3434
### Methods
3535

docs/Get started.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -36,8 +36,8 @@ Ackee will output the URL it's listening on once the server is running. Visit th
3636

3737
Ackee now runs on port `3000` and is only accessible from you local network. It's recommended to use a reverse proxy in front of Ackee. The following guides will help you through this steps.
3838

39-
- [SSL and HTTPS](./SSL%20and%20HTTPS.md)
40-
- [CORS headers](./CORS%20headers.md)
39+
- [SSL and HTTPS](SSL%20and%20HTTPS.md)
40+
- [CORS headers](CORS%20headers.md)
4141

4242
## With Docker
4343

@@ -88,8 +88,8 @@ Ackee will output the URL it's listening on once the server is running. Visit th
8888

8989
Ackee now runs on port `3000` and is only accessible from you local network. It's recommended to use a reverse proxy in front of Ackee. The following guides will help you through this steps.
9090

91-
- [SSL and HTTPS](./SSL%20and%20HTTPS.md)
92-
- [CORS headers](./CORS%20headers.md)
91+
- [SSL and HTTPS](SSL%20and%20HTTPS.md)
92+
- [CORS headers](CORS%20headers.md)
9393

9494
## Without Docker
9595

@@ -139,8 +139,8 @@ yarn start
139139

140140
Ackee now runs on port `3000` and is only accessible from you local network. It's recommended to use a reverse proxy in front of Ackee. The following guides will help you through this steps.
141141

142-
- [SSL and HTTPS](./SSL%20and%20HTTPS.md)
143-
- [CORS headers](./CORS%20headers.md)
142+
- [SSL and HTTPS](SSL%20and%20HTTPS.md)
143+
- [CORS headers](CORS%20headers.md)
144144

145145
## With Heroku
146146

@@ -152,4 +152,4 @@ Simply deploy to Heroku by clicking this button:
152152

153153
### 2. Configure Ackee
154154

155-
Ensure that you're using the correct CORS headers by setting [`ACKEE_ALLOW_ORIGIN`](CORS%20Headers.md#heroku-or-platforms-as-a-service-configuration).
155+
Ensure that you're using the correct CORS headers by setting [`ACKEE_ALLOW_ORIGIN`](CORS%20headers.md#heroku-or-platforms-as-a-service-configuration).

0 commit comments

Comments
 (0)