Skip to content

Commit c103f90

Browse files
committed
fix: update multiple server note in previous versions
1 parent a6db362 commit c103f90

File tree

3 files changed

+9
-9
lines changed

3 files changed

+9
-9
lines changed

1.0/getting-started/core-concepts.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@
77
Your Laravel application can have any number of JSON:API compliant
88
APIs. We refer to each API as a **Server**.
99

10-
You may not use multiple servers: a simple application
11-
may only have one server. However, there are a number of use cases where
12-
you may decide to implement multiple servers. For example:
10+
You may opt to not use multiple servers: a simple application will
11+
typically only have one server. However, there are a number of use cases
12+
where you may decide to implement multiple servers. For example:
1313

1414
- If you have a public-facing API, and a private API (e.g. only accessible
1515
by administrators).

2.0/getting-started/core-concepts.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@
77
Your Laravel application can have any number of JSON:API compliant
88
APIs. We refer to each API as a **Server**.
99

10-
You may not use multiple servers: a simple application
11-
may only have one server. However, there are a number of use cases where
12-
you may decide to implement multiple servers. For example:
10+
You may opt to not use multiple servers: a simple application will
11+
typically only have one server. However, there are a number of use cases
12+
where you may decide to implement multiple servers. For example:
1313

1414
- If you have a public-facing API, and a private API (e.g. only accessible
1515
by administrators).

3.0/getting-started/core-concepts.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@
77
Your Laravel application can have any number of JSON:API compliant
88
APIs. We refer to each API as a **Server**.
99

10-
You may opt to not use multiple servers: a simple application
11-
may only have one server. However, there are a number of use cases where
12-
you may decide to implement multiple servers. For example:
10+
You may opt to not use multiple servers: a simple application will
11+
typically only have one server. However, there are a number of use cases
12+
where you may decide to implement multiple servers. For example:
1313

1414
- If you have a public-facing API, and a private API (e.g. only accessible
1515
by administrators).

0 commit comments

Comments
 (0)