from e33ce98d2ee0950faa25ee908c6b74e64970b40a

msupply-foundation · Oct 2, 2024 · 9230bf2 · 9230bf2
1 parent f5b19bd
commit 9230bf2
Show file tree

Hide file tree

Showing 36 changed files with 20 additions and 21 deletions.
diff --git a/content/docs/dispensary/prescriptions.md b/content/docs/dispensary/prescriptions.md
@@ -269,17 +269,17 @@ Default value is `Any` when you are issuing units.
 
 This is a list of batch numbers that you have in store for this item:
 
-| Column              | Description                                                                                      |
-| :--------------------- | :----------------------------------------------------------------------------------------------- |
-| **Batch**              | Batch number. It is a designation given to products made in the same manufacturing run.         |
-| **Expiry**             | Expiry date of the batch (format: MM/YYYY)                                                      |
-| **Location**           | This is the name of the location where the item is stored if your inventory is managed with storage locations |         
-| **On Hold**            | Indicates whether a batch is on hold or not. You cannot issue a batch that is on hold.          |
-| **In Store (packs)**   | Total number of packs in your store                                                              |
-| **Available (packs)**  | Number of packs available (not already allocated to other shipments)                             |
-| **Pack Size**              | Quantity of units per pack                       |
-| **[Unit] Qty Issued**  | Total quantity of units to be issued                                                             |
-| **Pack Qty Issued**    | Number of packs to be issued                                                                     |
+| Column                | Description                                                                                                   |
+| :-------------------- | :------------------------------------------------------------------------------------------------------------ |
+| **Batch**             | Batch number. It is a designation given to products made in the same manufacturing run.                       |
+| **Expiry**            | Expiry date of the batch (format: MM/YYYY)                                                                    |
+| **Location**          | This is the name of the location where the item is stored if your inventory is managed with storage locations |
+| **On Hold**           | Indicates whether a batch is on hold or not. You cannot issue a batch that is on hold.                        |
+| **In Store (packs)**  | Total number of packs in your store                                                                           |
+| **Available (packs)** | Number of packs available (not already allocated to other invoices)                                           |
+| **Pack Size**         | Quantity of units per pack                                                                                    |
+| **[Unit] Qty Issued** | Total quantity of units to be issued                                                                          |
+| **Pack Qty Issued**   | Number of packs to be issued                                                                                  |
 
 ![List of available batch numbers](/docs/dispensary/images/prescription_additem_listofbatches.png)
 
@@ -307,19 +307,18 @@ You may see one or more warning messages on this screen:
 
 ![placeholder warning!](/docs/distribution/images/os_warning_placeholder.png)
 
-The warning is shown to let you know that not enough stock is available to fulfil your request. A placeholder quantity is added automatically so that you can keep track of the amount requested, while adding more stock (for example by using an internal order or inbound shipment).
+The warning is shown to let you know that not enough stock is available to fulfil your request. A placeholder quantity is added automatically so that you can keep track of the amount requested, while adding more stock (for example by using an Internal Order or Inbound Shipment).
 
 This image also shows the warning which lets you know that some stock lines are expired; this may be why the system did not auto-allocate particular stock lines.
-However you can still manually choose those lines and issue the expired stock! 
+However you can still manually choose those lines and issue the expired stock!
 
 ![pack sizes warning!](/docs/distribution/images/os_warning_pack_sizes.png)
 
 This warning tells you that because of the available pack sizes, the system has rounded up the quantity requested. In this example, there is no pack size that is less than `12`. There are packs of `20` available though, so when 12 tablets are requested, the system has rounded up the request to `2` packs of `20`.
 
-
 ![pack sizes warning!](/docs/distribution/images/os_warning_no_quantity.png)
 
-If you add an item, forget to enter a quantity to issue, and click `OK` you will see this warning message. It is informing you that there is no issue quantity; from here you can click `OK` again to confirm that you intended to enter `0`, in which case the window will close and a placeholder row will be added to the shipment. You can edit the row later and add a quantity. If you forget to add a quantity however, and confirm the shipment as allocated, this row will be removed!
+If you add an item, forget to enter a quantity to issue, and click `OK` you will see this warning message. It is informing you that there is no issue quantity; from here you can click `OK` again to confirm that you intended to enter `0`, in which case the window will close and a placeholder row will be added to the invoice. You can edit the row later and add a quantity. If you forget to add a quantity however, and confirm the invoice as allocated, this row will be removed!
 
 ### Issue a quantity of packs
 
@@ -414,7 +413,7 @@ Once an item has been added to your prescription, the status will automatically
 - Prescription status is now `PICKED`
 - You are now invited to confirm the prescription via the `Confirm Verified` button
 
-At this stage, you are still able to edit shipment lines, to add items or to delete existing lines.
+At this stage, you are still able to edit invoice lines, to add items or to delete existing lines.
 
 ### Verify the Prescription
 

diff --git a/content/docs/distribution/customer_returns.md b/content/docs/distribution/customer_returns.md
@@ -117,7 +117,7 @@ Often, you will be processing the return of goods that you sent via an Outbound
 1. In the `Customers` window, you will be presented with a list of available customers. You can select your customer from the list or you can filter by typing the customer name.
 
 <div class="imagetitle">
-In the below example, we are wanting to receive returned stock from <b>Tamaki Central Medical Store</b>. 
+In the below example, we are wanting to receive returned stock from <b>Slytherin Clinic</b>. 
 </div>
 
 ![Create Customer Return](/docs/distribution/images/ir_create.gif)
@@ -205,19 +205,19 @@ There are 5 status for the Customer Return:
 | **Delivered** | When you confirm that the return has been delivered                                                                   |
 | **Verified**  | When you have verified the Customer Return                                                                            |
 
-You probably noticed that two of the status values only apply to automatically created shipments. These are created by the system when another store in the system creates a Supplier Return to return stock to your store. If this is the case you'll see a message near the top of the page:
+You probably noticed that two of the status values only apply to automatically created returns. These are created by the system when another store in the system creates a Supplier Return to return stock to your store. If this is the case you'll see a message near the top of the page:
 
 ![Automatic IS message](/docs/distribution/images/ir_message_automatic.png)
 
 Note that this message appears differently if the status is `Delivered` or `Verified`
 
 ![Automatic IS message: delivered](/docs/distribution/images/ir_message_automatic_delivered.png)
 
-If, however, you've created an Inbound Shipment manually, then the following message shows:
+If, however, you've created an Customer Return manually, then the following message shows:
 
 ![Manual IS message](/docs/distribution/images/ir_message_manual.png)
 
-and you'll see that the status bar has only the status values which apply to this type of shipment.
+and you'll see that the status bar has only the status values which apply to this Customer Return.
 
 <figure align="center">
     <img src="/docs/distribution/images/ir_statussequence_manual.png" alt="Inbound Shipment Status Sequence (New & manual)" style="width:60%">
@@ -393,7 +393,7 @@ Once you have done this:
 - Return status is now `DELIVERED`
 
 <div class="note">
-In case your Customer Return is <b>automatic</b>, you cannot confirm its delivery unless the customer has confirmed its shipment. In other words, your shipment status has to be <code>SHIPPED</code> before you can confirm that you have received the returned goods. 
+In case your Customer Return is <b>automatic</b>, you cannot confirm its delivery unless the customer has confirmed its shipment. In other words, your return status has to be <code>SHIPPED</code> before you can confirm that you have received the returned goods. 
 </div>
 
 ![Alt Text](/docs/distribution/images/ir_confirmdelivered.gif)

diff --git a/content/docs/distribution/images/cust_gotocust2.png b/content/docs/distribution/images/cust_gotocust2.png
diff --git a/content/docs/distribution/images/gotoir.png b/content/docs/distribution/images/gotoir.png
diff --git a/content/docs/distribution/images/gotoos2.png b/content/docs/distribution/images/gotoos2.png
diff --git a/content/docs/distribution/images/ir_additem.gif b/content/docs/distribution/images/ir_additem.gif
diff --git a/content/docs/distribution/images/ir_additembutton.png b/content/docs/distribution/images/ir_additembutton.png
diff --git a/content/docs/distribution/images/ir_confirmdelivered.gif b/content/docs/distribution/images/ir_confirmdelivered.gif
diff --git a/content/docs/distribution/images/ir_create.gif b/content/docs/distribution/images/ir_create.gif
diff --git a/content/docs/distribution/images/ir_delete.gif b/content/docs/distribution/images/ir_delete.gif
diff --git a/content/docs/distribution/images/ir_deleteselectedlines.gif b/content/docs/distribution/images/ir_deleteselectedlines.gif
diff --git a/content/docs/distribution/images/ir_filter.gif b/content/docs/distribution/images/ir_filter.gif
diff --git a/content/docs/distribution/images/ir_filter_columns.gif b/content/docs/distribution/images/ir_filter_columns.gif
diff --git a/content/docs/distribution/images/ir_group_by_item.gif b/content/docs/distribution/images/ir_group_by_item.gif
diff --git a/content/docs/distribution/images/ir_message_automatic.png b/content/docs/distribution/images/ir_message_automatic.png
diff --git a/content/docs/distribution/images/ir_message_automatic_delivered.png b/content/docs/distribution/images/ir_message_automatic_delivered.png
diff --git a/content/docs/distribution/images/ir_message_manual.png b/content/docs/distribution/images/ir_message_manual.png
diff --git a/content/docs/distribution/images/ir_newreturn.png b/content/docs/distribution/images/ir_newreturn.png
diff --git a/content/docs/distribution/images/ir_sidepanel.gif b/content/docs/distribution/images/ir_sidepanel.gif
diff --git a/content/docs/distribution/images/req_gotoreq2.png b/content/docs/distribution/images/req_gotoreq2.png
diff --git a/content/docs/replenishment/images/clicknewreturn.png b/content/docs/replenishment/images/clicknewreturn.png
diff --git a/content/docs/replenishment/images/goto_rnr.png b/content/docs/replenishment/images/goto_rnr.png
diff --git a/content/docs/replenishment/images/gotoor.png b/content/docs/replenishment/images/gotoor.png
diff --git a/content/docs/replenishment/images/intord_access.png b/content/docs/replenishment/images/intord_access.png
diff --git a/content/docs/replenishment/images/is_gotois.png b/content/docs/replenishment/images/is_gotois.png
diff --git a/content/docs/replenishment/images/or_actions_deletelines.gif b/content/docs/replenishment/images/or_actions_deletelines.gif
diff --git a/content/docs/replenishment/images/or_additem.gif b/content/docs/replenishment/images/or_additem.gif
diff --git a/content/docs/replenishment/images/or_additembutton.png b/content/docs/replenishment/images/or_additembutton.png
diff --git a/content/docs/replenishment/images/or_confirmpicked.gif b/content/docs/replenishment/images/or_confirmpicked.gif
diff --git a/content/docs/replenishment/images/or_created.png b/content/docs/replenishment/images/or_created.png
diff --git a/content/docs/replenishment/images/or_delete.gif b/content/docs/replenishment/images/or_delete.gif
diff --git a/content/docs/replenishment/images/or_filter.png b/content/docs/replenishment/images/or_filter.png
diff --git a/content/docs/replenishment/images/or_filter_columns.gif b/content/docs/replenishment/images/or_filter_columns.gif
diff --git a/content/docs/replenishment/images/or_group_by_item.gif b/content/docs/replenishment/images/or_group_by_item.gif
diff --git a/content/docs/replenishment/images/or_sidepanel.gif b/content/docs/replenishment/images/or_sidepanel.gif
diff --git a/content/docs/replenishment/images/sup_gotosup.png b/content/docs/replenishment/images/sup_gotosup.png