Apply suggestions from code review

Co-authored-by: Erin Shaben <[email protected]>

Author: 0xLucca

develop/parachains/deployment/manage-coretime.md

@@ -21,27 +21,27 @@ pub fn transfer<T: Config>(region_id: RegionId, new_owner: T::AccountId)
 
 **Parameters:**
 
-- **`origin`**: Must be a signed origin of the account which owns the region `region_id`
-- **`region_id`**: The region whose ownership should change
-- **`new_owner`**: The new owner for the region
+- **`origin`**: Must be a signed origin of the account which owns the region `region_id`.
+- **`region_id`**: The region whose ownership should change.
+- **`new_owner`**: The new owner for the region.
 
 ## Partition
 
 Split a bulk coretime region into two non-overlapping regions at a specific time point. This operation divides a region temporally, creating two shorter regions that together span the same duration as the original.
 
 The [partition](https://paritytech.github.io/polkadot-sdk/master/pallet_broker/pallet/struct.Pallet.html#method.partition){target=\_blank} operation removes the original region and creates two new regions with the same owner and core mask. The first new region spans from the original start time to the pivot point, while the second spans from the pivot point to the original end time.
 
-This is useful when you want to use part of your allocated time immediately and reserve the remainder for later use, or when you want to sell or transfer only a portion of your time allocation.
+This is useful when you want to use part of your allocated time immediately and reserve the remainder for later use or when you want to sell or transfer only a portion of your time allocation.
 
 ```rust
 pub fn partition<T: Config>(region_id: RegionId, pivot: Timeslice)
 ```
 
 **Parameters:**
 
-- **`origin`**: Must be a signed origin of the account which owns the region `region_id`
-- **`region_id`**: The region which should be partitioned into two non-overlapping regions
-- **`pivot`**: The offset in time into the region at which to make the split
+- **`origin`**: Must be a signed origin of the account which owns the region `region_id`.
+- **`region_id`**: The region which should be partitioned into two non-overlapping regions.
+- **`pivot`**: The offset in time into the region at which to make the split.
 
 ## Interlace
 
@@ -57,28 +57,28 @@ pub fn interlace<T: Config>(region_id: RegionId, pivot: CoreMask)
 
 Parameters:
 
-- **`origin`**: Must be a signed origin of the account which owns the region `region_id`
-- **`region_id`**: The region which should become two interlaced regions of incomplete regularity
-- **`pivot`**: The interlace mask of one of the two new regions (the other is its partial complement)
+- **`origin`**: Must be a signed origin of the account which owns the region `region_id`.
+- **`region_id`**: The region which should become two interlaced regions of incomplete regularity.
+- **`pivot`**: The interlace mask of one of the two new regions (the other is its partial complement).
 
 ## Assign
 
 [Assign](https://paritytech.github.io/polkadot-sdk/master/pallet_broker/pallet/struct.Pallet.html#method.assign){target=\_blank} a bulk coretime region to a specific task for execution.
 
-This operation places an item in the workplan corresponding to the region's properties and assigns it to the target task. If the region's end time has already passed, the operation becomes a no-op. If the region's beginning has passed, it effectively starts from the next schedulable timeslice.
+This operation places an item in the work plan corresponding to the region's properties and assigns it to the target task. If the region's end time has already passed, the operation becomes a no-op. If the region's beginning has passed, it effectively starts from the next schedulable timeslice.
 
-Use this operation to execute your tasks on the allocated cores. Choose final assignment when you're certain about the task allocation, or provisional when you might need flexibility for later changes.
+Use this operation to execute your tasks on the allocated cores. Choose a final assignment when you're certain about the task allocation or provisional when you might need flexibility for later changes.
 
 ```rust
 pub fn assign<T: Config>(region_id: RegionId, task: TaskId, finality: Finality)
 ```
 
 **Parameters:**
 
-- **`origin`**: Must be a signed origin of the account which owns the region `region_id`
-- **`region_id`**: The region which should be assigned to the task
-- **`task`**: The task to assign
-- **`finality`**: Indication of whether this assignment is final or provisional
+- **`origin`**: Must be a signed origin of the account which owns the region `region_id`.
+- **`region_id`**: The region which should be assigned to the task.
+- **`task`**: The task to assign.
+- **`finality`**: Indication of whether this assignment is final or provisional.
 
 ## Pool
 
@@ -94,7 +94,7 @@ pub fn pool<T: Config>(region_id: RegionId, payee: T::AccountId, finality: Final
 
 **Parameters:**
 
-- **`origin`**: Must be a signed origin of the account which owns the region `region_id`
-- **`region_id`**: The region which should be assigned to the pool
-- **`payee`**: The account which can collect revenue from the usage of this region
-- **`finality`**: Indication of whether this pool assignment is final or provisional
+- **`origin`**: Must be a signed origin of the account which owns the region `region_id`.
+- **`region_id`**: The region which should be assigned to the pool.
+- **`payee`**: The account which can collect revenue from the usage of this region.
+- **`finality`**: Indication of whether this pool assignment is final or provisional.