Skip to content
This repository was archived by the owner on Jun 28, 2023. It is now read-only.

Commit fdde3d0

Browse files
author
Nicholas Dunham
authored
Merge pull request #256 from blange/patch-4
Update HowItWorks.CoreComponents.md
2 parents ad90ade + 19ff41c commit fdde3d0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

doc_source/HowItWorks.CoreComponents.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ DynamoDB supports two different kinds of primary keys:
5454

5555
DynamoDB uses the partition key value as input to an internal hash function\. The output from the hash function determines the partition \(physical storage internal to DynamoDB\) in which the item will be stored\. All items with the same partition key value are stored together, in sorted order by sort key value\.
5656

57-
In a table that has a partition key and a sort key, it's possible for two items to have the same partition key value\. However, those two items must have different sort key values\.
57+
In a table that has a partition key and a sort key, it's possible for multiple items to have the same partition key value\. However, those items must have different sort key values\.
5858

5959
The *Music* table described in [Tables, Items, and Attributes](#HowItWorks.CoreComponents.TablesItemsAttributes) is an example of a table with a composite primary key \(*Artist* and *SongTitle*\)\. You can access any item in the *Music* table directly, if you provide the *Artist* and *SongTitle* values for that item\.
6060

0 commit comments

Comments
 (0)