how do i fix this text? :(

[seallover]

hello! so, i (foolishly) used a layout builder, and the code came out slightly... wonky. i (somehow) managed to fix most of it, but couldn't figure out what was wrong with the "likes" part :( how do i fix this?? thank you in advance!!

[Dan Q]

Much easier to debug if you copy-paste us the code or, even better, put it online so we can look at it in a browser!

[seallover]

Much easier to debug if you copy-paste us the code or, even better, put it online so we can look at it in a browser!

ohhhhh i'm sorry!! do you mean linking the site itself by putting it online?? i'm still trying to learn what is what, hope it's not too stupid of a question! 

[Dan Q]

There are no stupid questions. We all get stuck sometimes!

Personally, I find seeing a problem on an actual web page easiest to debug. I can use the browser's debug tools (like Inspect Element and the like!) to instantly see why something is behaving the way it does.

If it's not online yet, copy-pasting the code into a [​code]...[​/code] block is second-best. It's much easier to read code when I can highlight it, copy-paste bits into another file, etc.

Working from a screenshot of code is hardest. After all, the problem might not even be in the bit that's in the screenshot! Maybe there's a stray bit of CSS somewhere that's affecting the problem element? Or maybe there's an element that didn't get closed properly half way up the page! This makes working from screenshots of code very hard!

So in short - for me at least:

1. A link to a broken web page is easiest to fix,
2. The code from a broken web page is next-easiest,
3. A screenshot of broken code is pretty difficult, and
4. A description of the problem with no context at all is a BIG challenge! (you do see people who say e.g. "my page is broken but it was fine yesterday; what changed?" and give no clues at all!)

[seallover]

There are no stupid questions. We all get stuck sometimes!

Personally, I find seeing a problem on an actual web page easiest to debug. I can use the browser's debug tools (like Inspect Element and the like!) to instantly see why something is behaving the way it does.

If it's not online yet, copy-pasting the code into a [​code]...[​/code] block is second-best. It's much easier to read code when I can highlight it, copy-paste bits into another file, etc.

Working from a screenshot of code is hardest. After all, the problem might not even be in the bit that's in the screenshot! Maybe there's a stray bit of CSS somewhere that's affecting the problem element? Or maybe there's an element that didn't get closed properly half way up the page! This makes working from screenshots of code very hard!

So in short - for me at least:

1. A link to a broken web page is easiest to fix,
2. The code from a broken web page is next-easiest,
3. A screenshot of broken code is pretty difficult, and
4. A description of the problem with no context at all is a BIG challenge! (you do see people who say e.g. "my page is broken but it was fine yesterday; what changed?" and give no clues at all!)

got it, thank you!! the problem is that there is too much space between the "likes" text and the part where i specify my likes, and i have no idea why/how that happened... hope that made sense! here's the link: https://f0li3-a-d3ux.neocities.org/