fixed image sizes

they were full width images in the browser, this fixes them so that they're at least viewable. We might want to play with this a bit but it's better than it was.

docs/Writerside/topics/resources/multiprocessing.md

@@ -3,4 +3,4 @@
 The multiprocessing option allows you to process multiple videos at the same time, decreasing the total processing time. Each process runs in a separate CPU core. You can set the number of CPU cores to use by changing the "Max Number of Processes to Use" option in the "2d Image Trackers" parameter group. The default is the maximum number of cores on your machine minus one, to account for the process the GUI is running in. In the example below, the machine has 8 cores total, and 7 show up as available. Freemocap will never create more processes than the number of videos in your active recording. If you would like to turn off multiprocessing entirely, you can set the "Max Number of Processes to Use" to one. 
 
 
-![MultiProcessing Parameter Screenshot](multiprocessing_crop_detail.png)
+![MultiProcessing Parameter Screenshot](multiprocessing_crop_detail.png){ width="450" }

docs/Writerside/topics/resources/reprojection_filtering.md

@@ -2,7 +2,7 @@
 
 Reprojection error filtering is an optional postprocessing step to the 3D triangulation stage of processing. It retriangulates outlier data from the 3d triangulation with the cameras contributing the most error removed. Reprojection error filtering is most effective when there is poor skeleton detection in one or more camera views. It is turned on and off in "Process Data" tab with the checkbox "Run Reprojection Error Filtering". It is turned off by default.
 
-![Detail of Reprojection Error Filtering Options](reprojection_filtering_crop_detail.png)
+![Detail of Reprojection Error Filtering Options](reprojection_filtering_crop_detail.png){ width="450" }
 
 ## What is Reprojection Error?
 "Reprojection error" is the distance between the originally measured point (i.e. a joint on the 2d skeleton) and the reconstructed 3d point reprojected back onto the original image. The intuition is that if the 3d reconstruction and original 2d track are perfect, then reprojection error will be zero. If it isn't, then there is some inaccuracy in either: the original 2d tracks (i.e. bad skeleton detection from one or more cameras), in the 3d reconstruction (i.e. bad camera calibration), or a combination of the two.

docs/Writerside/topics/resources/yolo_cropping.md

@@ -2,7 +2,7 @@
 
 YOLO cropping is a processing option that passes each video frame through YOLO v8's object detection model to find the most likely area of the person in the frame before passing the image to the pose estimation model. This can help reduce false positives during pose estimation and aid tracking subjects that are relatively small in the cameras field of view. This process increases the quality of the output data at the cost of increased processing time. It can be turned on and off in "Process Data" tab with the checkbox "Use YOLO Crop Method". It is turned off by default.
 
-![Detail of YOLO Crop Checkbox](YOLO_crop_detail.png)
+![Detail of YOLO Crop Checkbox](YOLO_crop_detail.png){ width="450" }
 
 ## How it Works
 The pose estimation models FreeMoCap uses are all set up to process a certain size of image. While you can pass any size of video into FreeMoCap, the images get downsized to a set image size (256x256 pixels for MediaPipe) before going into the pose estimation model. This can have a negative effect on the model's processing, especially if the subject doesn't take up most of the image.