Progress

docs/en/flashcards/flashcards.md

@@ -9,20 +9,27 @@ Two types of flashcards are supported:
 
 <div class="grid" markdown>
 
-!!! tip "Question & Answer"
+!!! note "Question & Answer"
 
     [Question & Answer](qanda-cards.md) flashcards are ones where the flashcard text contains both the question text and answer text.
+
+    ---
+    ![flashcard-qanda-example](https://github.com/user-attachments/assets/95f5ae9a-3093-400e-9ef4-a0ec829eabf7)
 
-!!! tip "Cloze"
+!!! note "Cloze"
 
     [Cloze](basic-cloze-cards.md) flashcards are ones where the flashcard text identifies parts of the text (e.g. a word or phrase) that is hidden 
     when the front of the card is shown. <br/>
     The hidden text is known as a `cloze deletion`.
+    ---
+    ![flashcard-cloze-example](https://github.com/user-attachments/assets/47f7403b-a34f-4458-a078-417fa1ea75c6)
 </div>
 
 !!! tip
     For guidelines on how to write and structure flashcards, see [Spaced Repetition Guides]( ../resources.md#flashcards)
 
+---
+
 ## Flashcard Text, Flashcards and Cards
 
 !!! note
@@ -51,6 +58,9 @@ A special scheduling option is available for the review of sibling cards.
 If the [Bury sibling cards until the next day]( ../plugin-settings.md#flashcard-review)) setting is turned on, 
 only one sibling card is available for review on a single day.
 
+---
+
+
 ## RTL Support
 
 There are two ways that the plugin can be used with RTL languages, such as Arabic, Hebrew, Persian (Farsi).
@@ -69,6 +79,8 @@ This is the same way text direction is specified to the `RTL Support` plugin.
 
 Note that there is no current support for cards with different text directions within the same note.
 
+---
+
 ## Card Maintenance
 
 ### Deleting cards

docs/en/user-doco-vault/.obsidian/app.json

@@ -1 +1,3 @@
-{}
+{
+  "promptDelete": false
+}

docs/en/user-doco-vault/.obsidian/plugins/obsidian-spaced-repetition/data.json

@@ -41,7 +41,7 @@
     "maxLinkFactor": 1,
     "showDebugMessages": false
   },
-  "buryDate": "2024-07-26",
+  "buryDate": "2024-07-27",
   "buryList": [],
   "historyDeck": null
 }

docs/en/user-doco-vault/.obsidian/workspace.json

@@ -13,7 +13,7 @@
             "state": {
               "type": "markdown",
               "state": {
-                "file": "User Guide/Context.md",
+                "file": "Computing/AWS/DynamoDB/94. DynamoDB Partitions and Primary Keys.md",
                 "mode": "source",
                 "source": false
               }
@@ -85,7 +85,7 @@
             "state": {
               "type": "backlink",
               "state": {
-                "file": "User Guide/Context.md",
+                "file": "Computing/AWS/DynamoDB/94. DynamoDB Partitions and Primary Keys.md",
                 "collapseAll": false,
                 "extraContext": false,
                 "sortOrder": "alphabetical",
@@ -102,7 +102,7 @@
             "state": {
               "type": "outgoing-link",
               "state": {
-                "file": "User Guide/Context.md",
+                "file": "Computing/AWS/DynamoDB/94. DynamoDB Partitions and Primary Keys.md",
                 "linksCollapsed": false,
                 "unlinkedCollapsed": true
               }
@@ -125,7 +125,7 @@
             "state": {
               "type": "outline",
               "state": {
-                "file": "User Guide/Context.md"
+                "file": "Computing/AWS/DynamoDB/94. DynamoDB Partitions and Primary Keys.md"
               }
             }
           },
@@ -156,10 +156,11 @@
       "obsidian-spaced-repetition:Review flashcards": false
     }
   },
-  "active": "abd0bfd3259ee283",
+  "active": "2cb81aad0c9cc3a2",
   "lastOpenFiles": [
-    "Math/Ellipse/Ellipse Equation.md",
     "User Guide/Context.md",
+    "Computing/AWS/DynamoDB/101. [HOL] Searching DynamoDB - Query API.md",
+    "Math/Ellipse/Ellipse Equation.md",
     "User Guide",
     "Computing/AWS/DynamoDB/files/Pasted image 20240508132354.png",
     "Computing/AWS/DynamoDB/files/Pasted image 20240508134406.png",
@@ -190,7 +191,6 @@
     "Computing/AWS/DynamoDB/104. DynamoDB Optimistic Locking and Conditional Updates.md",
     "Computing/AWS/DynamoDB/103. [HOL] Create LSI and GSI.md",
     "Computing/AWS/DynamoDB/102. DynamoDB LSI and GSI.md",
-    "Computing/AWS/DynamoDB/101. [HOL] Searching DynamoDB - Query API.md",
     "Computing/AWS/DynamoDB/100. [HOL] Searching DynamoDB - Scan API.md",
     "Computing/AWS/DynamoDB",
     "Computing/AWS/Section 8 - DynamoDB/files",

docs/en/user-doco-vault/Computing/AWS/DynamoDB/94. DynamoDB Partitions and Primary Keys.md

@@ -1,4 +1,4 @@
-#course/aws/developer-associate 
+#course/aws/dynamo-db
 
  Hi guys. In this lesson, we're going to cover DynamoDB Partitions and Primary Keys. And this stuff is really important to understand so you can design your table for throughput and also searchability. 
 
@@ -11,8 +11,12 @@
  A partition key must be a unique attribute such as a user ID. So every user will have their own individual ID. The value of the partition key is input to an internal hash function and that determines the partition or physical location on which the data is stored. If you're using the partition key as your primary key, we'll see what all this means in a moment, then no two items can have the same partition key. 
 
  So let's look at an example table. On the left hand side here, we have a partition key. Now, in this case this is using a post ID, so maybe it's something like a forum. And there's a unique ID for each entry in the forum. And then on the right we have the attributes. And those are the information associated with each of these entries in the table. 
-
- You can also have something called a composite key. That is a partition key plus a sort key in combination. So an example is a user posting to a forum. The partition key would be the user ID and the sort key would be the timestamp of the post. The two together mean that you can have multiple items in the table with the same partition key but they're going to have a different sort key and that creates uniqueness. Two items may have the same partition key but they must have a different sort key. 
+
+
+ You can also have something called a composite key. That is a partition key plus a ==sort key== in combination. 
+
+
+ So an example is a user posting to a forum. The partition key would be the user ID and the sort key would be the timestamp of the post. The two together mean that you can have multiple items in the table with the same partition key but they're going to have a different sort key and that creates uniqueness. Two items may have the same partition key but they must have a different sort key. 
 
  All items with the same partition key are stored together and then they're sorted according to the sort key value. So that's why I said it's important to understand how this works in terms of performance and searchability. Using a composite key allows you to store multiple items with the same partition key. If you don't have a composite key with a sort key then you can only ever have one item in the table for each partition key entry. So let's have a look at an example. We've got a partition key here which is the client ID. We've then got a sort key which is the created timestamp. And together they form the primary key or composite key as it has both a partition key and a sort key together.