Skip to content

Commit

Permalink
Minor grammar fixes
Browse files Browse the repository at this point in the history
  • Loading branch information
NathanBaulch committed Nov 7, 2022
1 parent 78eafe4 commit 1c50d3f
Show file tree
Hide file tree
Showing 16 changed files with 54 additions and 54 deletions.
2 changes: 1 addition & 1 deletion bash/enlighten/_client.sh
Original file line number Diff line number Diff line change
Expand Up @@ -379,7 +379,7 @@ the last reported interval."
"system_id=:[PATH] "
"user_id=:[QUERY] "
"start_date=:[QUERY] Start date for reporting period. The reporting period ends on the previous day of the next month; for example, a 'start_date' of 2011-07-20 returns data through 2011-06-19. When the
start date is the first of a calendar month, the end end date is the last day of that month."
start date is the first of a calendar month, the end date is the last day of that month."
)
_describe -t actions 'operations' _op_arguments -S '' && ret=0
;;
Expand Down
4 changes: 2 additions & 2 deletions bash/enlighten/client.sh
Original file line number Diff line number Diff line change
Expand Up @@ -977,7 +977,7 @@ This endpoint can return a response of Data Temporarily Unavailable." | paste -s
| paste -sd' ' | fold -sw 80 | sed '2,$s/^/ /'
echo -e " * ${GREEN}system_id${OFF} ${BLUE}[integer]${OFF} ${RED}(required)${OFF} ${CYAN}(default: null)${OFF} - ${YELLOW}Specify as: system_id=value${OFF}" | paste -sd' ' | fold -sw 80 | sed '2,$s/^/ /'
echo -e " * ${GREEN}start_date${OFF} ${BLUE}[string]${OFF} ${RED}(required)${OFF} ${CYAN}(default: null)${OFF} - Start date for reporting period. The reporting period ends on the previous day of the next month; for example, a 'start_date' of 2011-07-20 returns data through 2011-06-19. When the
start date is the first of a calendar month, the end end date is the last day of that month.${YELLOW} Specify as: start_date=value${OFF}" \
start date is the first of a calendar month, the end date is the last day of that month.${YELLOW} Specify as: start_date=value${OFF}" \
| paste -sd' ' | fold -sw 80 | sed '2,$s/^/ /'
echo ""
echo -e "${BOLD}${WHITE}Responses${OFF}"
Expand Down Expand Up @@ -1126,7 +1126,7 @@ by their end dates; therefore, the first interval returned is 5 minutes after th
The response includes intervals that have been reported for the requested period. Gaps in reporting are not filled with 0-value intervals. The dark hours on a system are an example of such a
gap, because the microinverters do not produce at night.
Sometimes a request cannot be processed because the requested dates are invalid for the the system in question. Examples include asking for stats starting at a time that is later than the
Sometimes a request cannot be processed because the requested dates are invalid for the system in question. Examples include asking for stats starting at a time that is later than the
system's last reported interval, or asking for stats before a system has started production. In cases such as these, the response code is '422' and the response body includes an error reason
as well as the parameters used to process the request.
Expand Down
4 changes: 2 additions & 2 deletions bash/enlighten/docs/DefaultApi.md
Original file line number Diff line number Diff line change
Expand Up @@ -294,7 +294,7 @@ Name | Type | Description | Notes
**userId** | **string** | | [default to null]
**systemId** | **integer** | | [default to null]
**startDate** | **string** | Start date for reporting period. The reporting period ends on the previous day of the next month; for example, a 'start_date' of 2011-07-20 returns data through 2011-06-19. When the
start date is the first of a calendar month, the end end date is the last day of that month. | [default to null]
start date is the first of a calendar month, the end date is the last day of that month. | [default to null]

### Return type

Expand Down Expand Up @@ -451,7 +451,7 @@ by their end dates; therefore, the first interval returned is 5 minutes after th
The response includes intervals that have been reported for the requested period. Gaps in reporting are not filled with 0-value intervals. The dark hours on a system are an example of such a
gap, because the microinverters do not produce at night.

Sometimes a request cannot be processed because the requested dates are invalid for the the system in question. Examples include asking for stats starting at a time that is later than the
Sometimes a request cannot be processed because the requested dates are invalid for the system in question. Examples include asking for stats starting at a time that is later than the
system's last reported interval, or asking for stats before a system has started production. In cases such as these, the response code is '422' and the response body includes an error reason
as well as the parameters used to process the request.

Expand Down
6 changes: 3 additions & 3 deletions csharp-netcore/enlighten/docs/DefaultApi.md
Original file line number Diff line number Diff line change
Expand Up @@ -671,7 +671,7 @@ namespace Example
var apiInstance = new DefaultApi(config);
var userId = 4d6a51330a; // string |
var systemId = 66; // int |
var startDate = Fri Jul 01 10:00:00 AEST 2011; // DateTimeOffset | Start date for reporting period. The reporting period ends on the previous day of the next month; for example, a `start_date` of 2011-07-20 returns data through 2011-06-19. When the start date is the first of a calendar month, the end end date is the last day of that month.
var startDate = Fri Jul 01 10:00:00 AEST 2011; // DateTimeOffset | Start date for reporting period. The reporting period ends on the previous day of the next month; for example, a `start_date` of 2011-07-20 returns data through 2011-06-19. When the start date is the first of a calendar month, the end date is the last day of that month.
try
{
Expand Down Expand Up @@ -714,7 +714,7 @@ catch (ApiException e)
|------|------|-------------|-------|
| **userId** | **string** | | |
| **systemId** | **int** | | |
| **startDate** | **DateTimeOffset** | Start date for reporting period. The reporting period ends on the previous day of the next month; for example, a `start_date` of 2011-07-20 returns data through 2011-06-19. When the start date is the first of a calendar month, the end end date is the last day of that month. | |
| **startDate** | **DateTimeOffset** | Start date for reporting period. The reporting period ends on the previous day of the next month; for example, a `start_date` of 2011-07-20 returns data through 2011-06-19. When the start date is the first of a calendar month, the end date is the last day of that month. | |

### Return type

Expand Down Expand Up @@ -1058,7 +1058,7 @@ catch (ApiException e)


Returns performance statistics for the specified system as reported by microinverters installed on the system. If the total duration requested is more than one day, returns one day of intervals. Intervals are 5 minutes in length and start at the top of the hour. Requests for times that do not fall on the 5-minute marks are rounded down. For example, a request for 08:01, 08:02, 08:03, or 08:04 is treated as a request for 08:00. Intervals are listed by their end dates; therefore, the first interval returned is 5 minutes after the requested start date. The response includes intervals that have been reported for the requested period. Gaps in reporting are not filled with 0-value intervals. The dark hours on a system are an example of such a gap, because the microinverters do not produce at night. Sometimes a request cannot be processed because the requested dates are invalid for the the system in question. Examples include asking for stats starting at a time that is later than the system's last reported interval, or asking for stats before a system has started production. In cases such as these, the response code is `422` and the response body includes an error reason as well as the parameters used to process the request. If the system doesn't have any microinverters installed, the response includes an empty intervals array. Under some conditions, data for a given period may be temporarily unavailable.
Returns performance statistics for the specified system as reported by microinverters installed on the system. If the total duration requested is more than one day, returns one day of intervals. Intervals are 5 minutes in length and start at the top of the hour. Requests for times that do not fall on the 5-minute marks are rounded down. For example, a request for 08:01, 08:02, 08:03, or 08:04 is treated as a request for 08:00. Intervals are listed by their end dates; therefore, the first interval returned is 5 minutes after the requested start date. The response includes intervals that have been reported for the requested period. Gaps in reporting are not filled with 0-value intervals. The dark hours on a system are an example of such a gap, because the microinverters do not produce at night. Sometimes a request cannot be processed because the requested dates are invalid for the system in question. Examples include asking for stats starting at a time that is later than the system's last reported interval, or asking for stats before a system has started production. In cases such as these, the response code is `422` and the response body includes an error reason as well as the parameters used to process the request. If the system doesn't have any microinverters installed, the response includes an empty intervals array. Under some conditions, data for a given period may be temporarily unavailable.

### Example
```csharp
Expand Down
Loading

0 comments on commit 1c50d3f

Please sign in to comment.