Fix spelling mistakes and attribute inconsistencies in documentation

- Fix typo: authenticaiton → authentication
- Fix typo: extented → extended
- Fix typo: specyfing → specifying
- Fix typo: existing → exciting
- Fix attribute names: created_by/updated_by → created_at/updated_at
- Fix grammar: will not returned → will not be returned
- Fix grammar: will not return → will now return
- Fix double period: SMS.. → SMS.
- Fix copy-paste errors in provider opening_hours descriptions

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: espen

changelog.md

@@ -46,7 +46,7 @@ Added booking status endpoint.
 
 **Expandable objects**
 
-The booking endpoint can now expand related objects such as resource and service using the `extented` paramater.
+The booking endpoint can now expand related objects such as resource and service using the `extended` parameter.
 
 **Webhook version 2**
 
@@ -105,7 +105,7 @@ Previously we retried 20 times for failed webhooks. This is now changed to 5 ret
 
 **Added national_id_no and multiple column search for people**
 
-Search can now be done on multiple columns by specyfing for example both email and phone number.
+Search can now be done on multiple columns by specifying for example both email and phone number.
 
 ## 2021-03-29
 
@@ -135,7 +135,7 @@ JSON is our only God now.
 
 *BREAKING CHANGE*
 
-All errors based on client request input will not return a 400 Bad Request status code instead of 403 Forbidden.
+All errors based on client request input will now return a 400 Bad Request status code instead of 403 Forbidden.
 
 **Lack of authorization now returns 403**
 

examples_private.md

@@ -151,7 +151,7 @@ Content-Type: application/json; charset=utf-8
 
 ### Initiate new booking for new customer
 
-Now the customer is ready to book. So existing!
+Now the customer is ready to book. So exciting!
 
 This is the first example where you will differentiate the request since the goal is to implement a custom booking site. The Makeplans booking site operates based on many settings and rules that define availability. Naturally existing bookings is taken into account so you do not get double bookings (it is possible to add double bookings, but not from the public booking site). And then there is the availability set for the resources; standard opening hours and opening hours set on specific dates. In addition you can set certain rules for when booking is allowed, for example only 2 months ahead or not the same day. You can also set the booking site to be closed during national holidays.
 But back to the API. When you make a request to create a new booking in the private API we will ignore most of these rules. These rules are only applicable on the public booking site. So it is very important that you add `public_booking=true` to the request to ensure booking are only allowed during the rules and availability you set on your account and resources. Unless you are authenticated your customers in your app it is also recommended that you let Makeplans handle verification. We will send an SMS that the customer needs to verify to confirm the booking.

readme.md

@@ -112,7 +112,7 @@ Custom data is stored as key/value. All values are stored as strings but we do c
 
 ## Authentication
 
-Only the private API requires authentication. If you intend to use the API on a website please use the [public API](#public-and-private-api) which does not require authenticaiton.
+Only the private API requires authentication. If you intend to use the API on a website please use the [public API](#public-and-private-api) which does not require authentication.
 
 Use your account API-Key to authenticate with the Makeplans API. First enable the API on the account and you will find the API-Key in the account settings.
 
@@ -407,8 +407,8 @@ Response
 <table>
   <tr><th>Name</th><th>Type</th><th>Description</th></tr>
   <tr><td>id</td><td>Integer</td><td>Automatically set</td></tr>
-  <tr><td>created_by</td><td>DateTime</td><td>Automatically set</td></tr>
-  <tr><td>updated_by</td><td>DateTime</td><td>Automatically set</td></tr>
+  <tr><td>created_at</td><td>DateTime</td><td>Automatically set</td></tr>
+  <tr><td>updated_at</td><td>DateTime</td><td>Automatically set</td></tr>
   <tr><td>service_id</td><td>Integer</td><td>Not required</td></tr>
   <tr><td>event_id</td><td>Integer</td><td>Not required</td></tr>
   <tr><td>resource_id</td><td>Integer</td><td>Required</td></tr>
@@ -685,7 +685,7 @@ See [information about additional parameters](#additional-parameters).
 <table>
   <tr><th>Name</th><th>Type</th><th>Description</th></tr>
   <tr><td>cancellation_send_email</td><td>Boolean</td><td>Send out cancellation email.</td></tr>
-  <tr><td>cancellation_send_sms</td><td>Boolean</td><td>Send out cancellation SMS..</td></tr>
+  <tr><td>cancellation_send_sms</td><td>Boolean</td><td>Send out cancellation SMS.</td></tr>
 </table>
 
 ### Update booking
@@ -1152,7 +1152,7 @@ Response
 
 ### Delete resource
 
-`DELETE /resources/{resource_id}` will delete existing resource with id `{resource_id}`. Deleting a resource will set it to active=false and will not returned in any listings.
+`DELETE /resources/{resource_id}` will delete existing resource with id `{resource_id}`. Deleting a resource will set it to active=false and will not be returned in any listings.
 
 ### Get opening hours for specific dates
 
@@ -1313,12 +1313,12 @@ Resources provides services. This link is called a provider.
   <tr><td>resource_id</td><td>Integer</td><td>Required</td></tr>
   <tr><td>service_id</td><td>Integer</td><td>Required</td></tr>
   <tr><td>opening_hours_mon</td><td>Array</td><td>Opening hours for Monday. Fallback to resource availability.</td></tr>
-  <tr><td>opening_hours_tue</td><td>Array</td><td>Opening hours for Monday. Fallback to resource availability..</td></tr>
-  <tr><td>opening_hours_wed</td><td>Array</td><td>Opening hours for Monday. Fallback to resource availability.</td></tr>
-  <tr><td>opening_hours_thu</td><td>Array</td><td>Opening hours for Monday. Fallback to resource availability.</td></tr>
-  <tr><td>opening_hours_fri</td><td>Array</td><td>Opening hours for Monday. Fallback to resource availability.</td></tr>
-  <tr><td>opening_hours_sat</td><td>Array</td><td>Opening hours for Monday. Fallback to resource availability.</td></tr>
-  <tr><td>opening_hours_sun</td><td>Array</td><td>Opening hours for Monday. Fallback to resource availability.</td></tr>
+  <tr><td>opening_hours_tue</td><td>Array</td><td>Opening hours for Tuesday. Fallback to resource availability.</td></tr>
+  <tr><td>opening_hours_wed</td><td>Array</td><td>Opening hours for Wednesday. Fallback to resource availability.</td></tr>
+  <tr><td>opening_hours_thu</td><td>Array</td><td>Opening hours for Thursday. Fallback to resource availability.</td></tr>
+  <tr><td>opening_hours_fri</td><td>Array</td><td>Opening hours for Friday. Fallback to resource availability.</td></tr>
+  <tr><td>opening_hours_sat</td><td>Array</td><td>Opening hours for Saturday. Fallback to resource availability.</td></tr>
+  <tr><td>opening_hours_sun</td><td>Array</td><td>Opening hours for Sunday. Fallback to resource availability.</td></tr>
 </table>
 
 Opening hours for a provider works in the same way as availability is defined on [resource exception date](#resource-exception-date).